From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail05.groups.io (mail05.groups.io [45.79.224.7]) by spool.mail.gandi.net (Postfix) with ESMTPS id E65DB941AA6 for ; Wed, 15 Jan 2025 18:52:56 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=DFCSgHhi8OdiHVy5/guiUqFXgWwq43n4OB28oNxtVM4=; c=relaxed/simple; d=groups.io; h=Date:Message-Id:Subject:From:Mime-Version:To:Cc:References:In-Reply-To:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Resent-Date:Resent-From:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Type; s=20240830; t=1736967176; v=1; x=1737226375; b=DI5vU6p//iuVZoya/3YwJUCXtUdnV823eBsZnYDV+rh2biHyqkn+OfhRq83UNRQwS/uaqNNt VaTTo0G+fA/bSy38OH0QKi/G6kbgSuOaZoz+YqCZRQr6EcG6MabTAWTtNaljZhF97BYZPfwL8by fq1VQbZfYh49YpevIAO4q5n7Icsq+B3CJ6stLL46l2oaSb/wJD2Z+5RxeOg0sDI46skdTYvqKut NVr5odEkhppDtgW1hixxLkA6COq5NqjxkzI8h6xsm1uOby5Es4GHZG+u4pl/82Xskvh20BYm+3c d+xqL/2wa1FvIg80af3y+JQF83YDX7p+M0qX2yDFeAg0g== X-Received: by 127.0.0.2 with SMTP id vHFNYY7687511xiKjTCkY1Zy; Wed, 15 Jan 2025 10:52:55 -0800 X-Received: from va-2-31.ptr.blmpb.com (va-2-31.ptr.blmpb.com [209.127.231.31]) by mx.groups.io with SMTP id smtpd.web11.16170.1736332017368921001 for ; Wed, 08 Jan 2025 02:26:58 -0800 Date: Wed, 08 Jan 2025 18:26:42 +0800 Message-Id: <94ba23fe064f2d82b913d4850e73e1d7918b1915.2ab9d557.6255.4c20.a423.6b6b95573d20@feishu.cn> Subject: Re: [edk2-devel] Expansion of ARCH in .dsc files From: "Ajan Zhong" Mime-Version: 1.0 X-Lms-Return-Path: To: "Leif Lindholm" Cc: "Joey Vagedes" , "devel@edk2.groups.io" , "Ard Biesheuvel" , "Kinney, Michael D" References: <94ba23fe064f2d82b913d4850e73e1d7918b1915.e524b174.0181.4a50.a951.515098c6ec72@feishu.cn> In-Reply-To: <94ba23fe064f2d82b913d4850e73e1d7918b1915.e524b174.0181.4a50.a951.515098c6ec72@feishu.cn> Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Resent-Date: Wed, 15 Jan 2025 10:52:51 -0800 Resent-From: ajan.zhong@newfw.com Reply-To: devel@edk2.groups.io,ajan.zhong@newfw.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: MbYA2cvcr466CIgTaR8vj3CCx7686176AA= Content-Type: multipart/alternative; boundary=aea3261dbf22603b4d0b77d2e82bcb3b5a77f693197da48df6073df8baa0 X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20240830 header.b="DI5vU6p/"; dmarc=none; spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 45.79.224.7 as permitted sender) smtp.mailfrom=bounce@groups.io --aea3261dbf22603b4d0b77d2e82bcb3b5a77f693197da48df6073df8baa0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Hi all, Just check outputs for each architecture, the FV cannot be generated if we = use this method: [Defines.X64] OUTPUT_DIRECTORY =3D Build/UefiPayloadPkgX64 FLASH_DEFINITION =3D UefiPayloadPkg/UefiPayloadPkg.fdf If we place FLASH_DEFINITION under the Defines section: [Defines] FLASH_DEFINITION =3D UefiPayloadPkg/UefiPayloadPkg.fdf We will meet "error F003: Module built under multiple ARCHs ['AARCH64', 'X6= 4']. Not able to determine which output to put into flash for Module MdeMod= ulePkg/Universal/DevicePathDxe/DevicePathDxe.inf !"=C2=A0issue again. Still working in progress to figure out other solutions. > From: "Ajan Zhong" > Date:=C2=A0 Wed, Jan 8, 2025, 3:29 PM > Subject:=C2=A0 Re: [EXTERNAL] [edk2-devel] Expansion of ARCH in .dsc file= s > To: "Leif Lindholm" > Cc: "Joey Vagedes", "devel@edk2.groups.io", "Ard Biesheuvel", "Kinney, M= ichael D" > Thanks Leif and Joey. :) >=20 >=20 > As suggested, I used the following content in the DSC file to pass all th= e builds: >=20 >=20 > [Defines.IA32] > OUTPUT_DIRECTORY =3D Build/UefiPayloadPkgIA32 > FLASH_DEFINITION =3D UefiPayloadPkg/UefiPayloadPkg.fdf > [Defines.X64] > OUTPUT_DIRECTORY =3D Build/UefiPayloadPkgX64 > FLASH_DEFINITION =3D UefiPayloadPkg/UefiPayloadPkg.fdf > [Defines.AARCH64] > OUTPUT_DIRECTORY =3D Build/UefiPayloadPkgAARCH64 > FLASH_DEFINITION =3D UefiPayloadPkg/UefiPayloadPkg.fdf >=20 >=20 > I have tried following build commands, they all succeed to build correspo= nding binaries: > 1. build -p UefiPayloadPkg/UefiPayloadPkg.dsc -b DEBUG -a IA32 -a X64 -a = AARCH64 -t GCC5 > 2. python UefiPayloadPkg/UniversalPayloadBuild.py=C2=A0-t GCC5 -b DEBUG --FIT > 3. python UefiPayloadPkg/UniversalPayloadBuild.py=C2=A0-t GCC5 -a IA32 -b DEBUG --FIT > 4. python UefiPayloadPkg/UniversalPayloadBuild.py=C2=A0-t GCC5 -a AARCH -b DEBUG --FIT >=20 >=20 > Now I am creating a new draft PR to fix all github CI failures which are = not generated in my local. >=20 >=20 > Thanks again for your help. > From: "Leif Lindholm" > Date:=C2=A0 Wed, Jan 8, 2025, 4:14 AM > Subject:=C2=A0 Re: [EXTERNAL] [edk2-devel] Expansion of ARCH in .dsc file= s > To: "Joey Vagedes" > Cc: "devel@edk2.groups.io", "Ajan Zhong", "Ard Biesheuvel", "Kinney, Michael = D" > Hi Joey,=C2=A0 >=20 >=20 > I appreciate the pointer.=C2=A0 > However, that's the .inf spec.=C2=A0 >=20 >=20 > The same language is not in the corresponding section of=C2=A0 > https://tianocore-docs.github.io/edk2-DscSpecification/release-1.28/3_edk= _ii_dsc_file_format/35_[defines]_section.html#35-defines-section=C2=A0 >=20 >=20 > Regards,=C2=A0 >=20 >=20 > Leif=C2=A0 >=20 >=20 > On Tue, 7 Jan 2025 at 19:43, Joey Vagedes wro= te:=C2=A0 > >=C2=A0 > > Leif,=C2=A0 > >=C2=A0 > > For your awareness, Section 3.4 of the INF specification states that ar= chitectural modifiers for the [Defines] section tag are not permitted.=C2= =A0 > >=C2=A0 > > So that you can Ctrl+F and to find the exact language, here is a quote:= =C2=A0 > >=C2=A0 > > "architectural modifiers for the [Defines] section tag are not permitte= d"=C2=A0 > >=C2=A0 > > https://tianocore-docs.github.io/edk2-InfSpecification/release-1.27/3_e= dk_ii_inf_file_format/34_[defines]_section.html#34-defines-section=C2=A0 > >=C2=A0 > > Thanks,=C2=A0 > > Joey=C2=A0 > >=C2=A0 > > -----Original Message-----=C2=A0 > > From: devel@edk2.groups.io=C2=A0 On Behalf Of Lei= f Lindholm via groups.io=C2=A0 > Sent: Tuesday, January 7, 2025 11:05 AM=C2=A0 > > To: devel@edk2.groups.io=C2=A0 > Cc: Ajan Zhong ; Ard Biesheuvel ; Kinney, Michael D =C2=A0 > > Subject: [EXTERNAL] [edk2-devel] Expansion of ARCH in .dsc files=C2=A0 > >=C2=A0 > > So... I originally tripped over my misunderstanding of when w= riting=C2=A0 > > https://github.com/tianocore/edk2/pull/6262=C2=A0to get around somethin= g I wanted to test in UefiPayloadPkg.=C2=A0 > >=C2=A0 > > Now Ajan has run into at least an adjacent problem when trying to rewor= k=C2=A0 > > https://github.com/tianocore/edk2/pull/6545=C2=A0based on feedback I am= ong others provided.=C2=A0 > >=C2=A0 > > Now, the thing I had misunderstood before is that when build is called = with multiple -a options, the ARCH variable will expand to a space-separate= d list of *all* the specified architectures.=C2=A0 > > A lot of Arm/AArch64 modules assume this variable only ever contains a = single architecture.=C2=A0 > >=C2=A0 > > The thing is, I don't think this is clearly documented in the .dsc spec= ification at all. And it is frequently used as=C2=A0a=C2=A0shorthand in the= re in a form that would only work if build was called with a single -a.=C2= =A0 > > Now, this also means that there are nearly no correct users of ARCH in= =C2=A0 > > edk2 or edk2-platforms.=C2=A0 > > Because "the list of all architectures being built simultaneously"=C2= =A0 > > simply isn't very useful information=C2=A0 > > build-time. There are two correct uses in edk2, in EmulatorPkg.dsc and = in UefiPayloadPkg.dsc, using '!if "IA32" in "$ARCH"', which as far as I can= tell is the only possible way to use the variable correctly.=C2=A0 > > Slightly amusingly, EmulatorPkg.dsc also contains an incorrect use.=C2= =A0 > >=C2=A0 > > I guess the behaviour is a direct result of how the build command is ar= chitected.=C2=A0 > > I guess the one question I have is - is this the intended behaviour?=C2= =A0 > >=C2=A0 > > Ard: I think we need to update some of our .dsc files...=C2=A0 > >=C2=A0 > > Ajan: one somewhat hacky workaround I can think of to separate=C2=A0the= output images is to hardcode the output image name in arch-specific Define= s sections, like so:=C2=A0 > >=C2=A0 > > diff --git a/ArmVirtPkg/ArmVirtQemu.dsc b/ArmVirtPkg/ArmVirtQemu.dsc in= dex 0bd8d85cab03..f07f2b91764e 100644=C2=A0 > > --- a/ArmVirtPkg/ArmVirtQemu.dsc=C2=A0 > > +++ b/ArmVirtPkg/ArmVirtQemu.dsc=C2=A0 > > @@ -12,12 +12,17 @@=C2=A0 > >=C2=A0 # Defines Section - statements that will be processed to create a= Makefile.=C2=A0 > >=C2=A0 #=C2=A0 > >=C2=A0 #################################################################= ###############=C2=A0 > > +[Defines.ARM]=C2=A0 > > +=C2=A0 OUTPUT_DIRECTORY =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =3D Build/ArmVirtQemu-ARM=C2=A0 > > +=C2=A0 > > +[Defines.AARCH64]=C2=A0 > > +=C2=A0 OUTPUT_DIRECTORY =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =3D Build/ArmVirtQemu-AARCH64=C2=A0 > > +=C2=A0 > >=C2=A0 [Defines]=C2=A0 > > =C2=A0=C2=A0 PLATFORM_NAME =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0=C2=A0 =3D ArmVirtQemu=C2=A0 > > =C2=A0=C2=A0 PLATFORM_GUID =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0=C2=A0 =3D 37d7e986-f7e9-45c2-8067-e371421a626c=C2=A0 > > =C2=A0=C2=A0 PLATFORM_VERSION =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =3D 0.1=C2=A0 > > =C2=A0=C2=A0 DSC_SPECIFICATION =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0=C2=A0 =3D 0x00010005=C2=A0 > > -=C2=A0 OUTPUT_DIRECTORY =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =3D Build/ArmVirtQemu-$(ARCH)=C2=A0 > > =C2=A0=C2=A0 SUPPORTED_ARCHITECTURES =C2=A0 =C2=A0 =C2=A0=C2=A0 =3D AAR= CH64|ARM=C2=A0 > > =C2=A0=C2=A0 BUILD_TARGETS =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0=C2=A0 =3D DEBUG|RELEASE|NOOPT=C2=A0 > > =C2=A0=C2=A0 SKUID_IDENTIFIER =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =3D DEFAULT=C2=A0 > >=C2=A0 > >=C2=A0 > > =C2=A0 > >=C2=A0 > > >=20 >=20 -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#120998): https://edk2.groups.io/g/devel/message/120998 Mute This Topic: https://groups.io/mt/110483263/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- --aea3261dbf22603b4d0b77d2e82bcb3b5a77f693197da48df6073df8baa0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8
Hi all,
Just check outputs for each architecture, the FV cann= ot be generated if we use this method:
= [Defines.X64]
OUTPUT_DIRECTORY =3D Build/UefiPayloadPkgX64<= /span>
FLASH_DEFINITION =3D UefiPayloadPkg= /UefiPayloadPkg.fdf

If we place FLASH_DEFINITION under the= Defines section:
[Defines]=
FLASH_DEFINITION =3D UefiPayloadPkg= /UefiPayloadPkg.fdf
We will mee= t "error F003: Module built under multiple ARCHs ['AAR= CH64', 'X64']. Not able to determine which output to put into f= lash for Module MdeModulePkg/Universal/DevicePathDxe/DevicePathDxe.inf != 4;=C2=A0issue again.

Still working in progress to figure out ot= her solutions.

=
From: &= #34;Ajan Zhong"<ajan.zhong@newfw.= com>
Date:=C2=A0 Wed, Jan 8, 2025, 3:29= PM
Subject:=C2=A0 Re: [EXTERNAL] [edk2-devel]= Expansion of ARCH in .dsc files
To: "Leif= Lindholm"<leif.lindhol= m@oss.qualcomm.com>
Cc: "Joey Vaged= es"<joeyvagedes@microsoft.co= m>, "devel@edk2.groups.io"<devel@edk2.groups.io>, "Ard Bie= sheuvel"<ardb+tianocore@ke= rnel.org>, "Kinney, Michael D"<michael.d.kinney@intel.com>
Thanks Leif and Joey. :)

As suggested, I used the following conten= t in the DSC file to pass all the builds:
=
[Defines.IA32]
OUTPUT_DIRECTORY =3D Build/UefiPayloadPkgIA32
FLASH_DEFINITION = =3D UefiPayloadPkg/UefiPayloadPkg.fdf
[Defines.X64]
OUTPUT_DI= RECTORY =3D Build/UefiPayloadPkgX64
=
FLASH_DEFINITION =3D UefiPayload= Pkg/UefiPayloadPkg.fdf
[Defines.AARCH64]<= /div>
<= span style=3D"background-color: rgb(255, 255, 255);">OUTPUT_DIRECTORY =3D B= uild/UefiPayloadPkgAARCH64
FLASH_DEFINITION =3D UefiPayloadPkg/UefiPa= yloadPkg.fdf

I have tried following build commands, they all = succeed to build corresponding binaries:
<= /div>
  1. build -p UefiPayloadPkg/UefiPayloadPkg.d= sc -b DEBUG -a IA32 -a X64 -a AARCH64 -t GCC5
  2. p= ython UefiPayloadPkg/UniversalPayloadBuild.py=C2=A0-t GCC5 -b DEBUG --FIT=
  3. python UefiPayloadPkg/UniversalPayloadBuild.py=C2=A0-t GCC5 -a IA32 -b DEBUG --FIT
  4. python UefiPayloadPkg/= UniversalPayloadBuild.py=C2=A0-t GCC5 -a AARCH = -b DEBUG --FIT

Now I am creating a new draft PR to fix all github CI failures whi= ch are not generated in my local.

Thanks again for your help.
From: "Leif Lindholm"<leif.lindholm@oss.qualcomm.com>
Date:=C2=A0 Wed, Jan 8, 2025, 4:14 AM
S= ubject:=C2=A0 Re: [EXTERNAL] [edk2-devel] Expansion of ARCH in .dsc files
<= div class=3D"" dir=3D"auto">To: "Joey Vagedes"<joeyvagedes@microsoft.com>
Cc: "devel@edk2.groups.io= "<devel@edk2.groups.io>= ;, "Ajan Zhong"<ajan.zhong@ne= wfw.com>, "Ard Biesheuvel"<ardb+tianocore@kernel.org>, "Kinney, Michael D"<= ;michael.d.kinney@intel.com>= ;
Hi Joey,=C2=A0

I appreciate the pointer.=C2=A0
<= /div>
Howe= ver, that's the .inf spec.=C2=A0

The same language is not i= n the corresponding section of=C2=A0
https://tianocore-docs.github.= io/edk2-DscSpecification/release-1.28/3_edk_ii_dsc_file_format/35_[defi= nes]_section.html#35-defines-section=C2=A0

Regards,=C2=A0
<= /div>

Leif=C2=A0

On Tue, 7 Jan 2025 at 19:43, Joey Vagedes <joeyvagedes@microsoft.com> wrote:=C2=A0
>=C2=A0<= /div>
>=C2=A0
> For your awareness, Section 3.4 o= f the INF specification states that architectural modifiers for the [Define= s] section tag are not permitted.=C2=A0
>=C2=A0
<= div class=3D"" dir=3D"auto" style=3D"font-size: 14px;">> So that you can= Ctrl+F and to find the exact language, here is a quote:=C2=A0
<= div data-zone-id=3D"0" data-line-index=3D"65" data-line=3D"true" style=3D"m= argin-top: 4px; margin-bottom: 4px; line-height: 1.6;" class=3D"history-quo= te-line">
>=C2=A0=
> "architectural modifiers for the [Defines] section tag are no= t permitted"=C2=A0
>=C2=A0
> https://tianocore-docs.= github.io/edk2-InfSpecification/release-1.27/3_edk_ii_inf_file_format/34_[defines]_section.html#34-defines-section=C2=A0
>=C2=A0
<= div data-zone-id=3D"0" data-line-index=3D"70" data-line=3D"true" style=3D"m= argin-top: 4px; margin-bottom: 4px; line-height: 1.6;" class=3D"history-quo= te-line">
> Thank= s,=C2=A0
>=C2=A0
> -----Original Message-----= =C2=A0
> To: devel@edk2.groups.io=C2=A0
> Cc: Ajan Zhong <ajan.zhong@newfw.com>;= Ard Biesheuvel <ardb+tianocore@kernel.org>; Kin= ney, Michael D <michael.d.kinney@intel.com>=C2= =A0
> Subject: [EXTERNAL] [edk2-devel] Expansion of ARCH in .dsc files= =C2=A0
>=C2=A0
> So... I originally tripped over my misunderstan= ding of <subject> when writing=C2=A0
> https://github.com/tianocore/edk2/pull/6262=C2=A0to get around some= thing I wanted to test in UefiPayloadPkg.=C2=A0
>=C2=A0
> Now Aja= n has run into at least an adjacent problem when trying to rework=C2=A0
&= gt; https://github.com/tianocore/edk2/pull/6545= =C2=A0based on feedback I among others provided.=C2=A0
>=C2=A0
&= gt; Now, the thing I had misunderstood before is that when build is called = with multiple -a options, the ARCH variable will expand to a space-separate= d list of *all* the specified architectures.=C2=A0
> A lot of Arm/AArc= h64 modules assume this variable only ever contains a single architecture.= =C2=A0
>=C2=A0
> The thing is, I don't think this is clearly= documented in the .dsc specification at all. And it is frequently used as= =C2=A0a=C2=A0shorthand in there in a form that would only work if build was= called with a single -a.=C2=A0
> Now, this also means that there are = nearly no correct users of ARCH in=C2=A0
> edk2 or edk2-platforms.=C2= =A0
> Because "the list of all architectures being built simultane= ously"=C2=A0
> simply isn't very useful information=C2=A0
&g= t; build-time. There are two correct uses in edk2, in EmulatorPkg.dsc and i= n UefiPayloadPkg.dsc, using '!if "IA32" in "$ARCH"'= , which as far as I can tell is the only possible way to use the variable c= orrectly.=C2=A0
> Slightly amusingly, EmulatorPkg.dsc also contains an= incorrect use.=C2=A0
>=C2=A0
> I guess the behaviour is a direct= result of how the build command is architected.=C2=A0
> I guess the o= ne question I have is - is this the intended behaviour?=C2=A0
>=C2=A0<= /div>
> Ard: I think we need to update some of our .dsc files...=C2=A0
>=C2=A0
> Ajan: one somewhat hacky workaround I can think of to s= eparate=C2=A0the output images is to hardcode the output image name in arch= -specific Defines sections, like so:=C2=A0
>=C2=A0
> diff --git= a/ArmVirtPkg/ArmVirtQemu.dsc b/ArmVirtPkg/ArmVirtQemu.dsc index 0bd8d85cab= 03..f07f2b91764e 100644=C2=A0
> --- a/ArmVirtPkg/ArmVirtQemu.dsc=C2= =A0
> +++ b/ArmVirtPkg/ArmVirtQemu.dsc=C2=A0
> @@ -12,12 +12,17= @@=C2=A0
>=C2=A0 # Defines Section - statements that will be process= ed to create a Makefile.=C2=A0
>=C2=A0 #=C2=A0
=
>=C2=A0 ########= ########################################################################=C2= =A0
> +[Defines.ARM]=C2=A0
> +=C2=A0 OUTPUT_DIRECTORY =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D Build/ArmVirtQemu-ARM=C2=A0
> +[Defines.AARCH64]=C2=A0
> +=C2=A0 OUTPUT_DIRE= CTORY =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D Build/ArmVirtQem= u-AARCH64=C2=A0
> +=C2=A0
>=C2=A0 [Defines]=C2=A0
=
> =C2= =A0=C2=A0 PLATFORM_NAME =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0=C2=A0 =3D ArmVirtQemu=C2=A0
> =C2=A0=C2=A0 PLATFORM_GUID =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =3D 37d7e986-f7e= 9-45c2-8067-e371421a626c=C2=A0
> =C2=A0=C2=A0 PLATFORM_VERSION =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D 0.1=C2=A0
> =C2=A0=C2= =A0 DSC_SPECIFICATION =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =3D 0= x00010005=C2=A0
> -=C2=A0 OUTPUT_DIRECTORY =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =3D Build/ArmVirtQemu-$(ARCH)=C2=A0
> =C2=A0= =C2=A0 SUPPORTED_ARCHITECTURES =C2=A0 =C2=A0 =C2=A0=C2=A0 =3D AARCH64|ARM= =C2=A0
> =C2=A0=C2=A0 BUILD_TARGETS =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =3D DEBUG|RELEASE|NOOPT=C2=A0
> =C2=A0= =C2=A0 SKUID_IDENTIFIER =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =3D DEFAULT=C2=A0
>=C2=A0
>=C2=A0
> =C2=A0
<= div data-zone-id=3D"0" data-line-index=3D"135" data-line=3D"true" style=3D"= margin-top: 4px; margin-bottom: 4px; line-height: 1.6;" class=3D"history-qu= ote-line">
>=C2= =A0
>

_._,_._,_
Groups.io Links:

=20 You receive all messages sent to this group. =20 =20

View/Reply Online (#120998) | =20 | Mute= This Topic | New Topic
Your Subscriptio= n | Contact Group Owner | Unsubscribe [rebecca@openfw.io]

_._,_._,_
--aea3261dbf22603b4d0b77d2e82bcb3b5a77f693197da48df6073df8baa0--