Thanks all.

I checked packages which support multiple architectures (IA32 and X64), all these modules generate only one flash image for one architecture. And checked build process python scripts, we have no other way to build IA32/X64/AARCH64 at same time.

As suggested, I plan to update azure Ubuntu GCC5 pipeline to adapt this scenario. And will provide feedback after validation.

From: "Leif Lindholm"<leif.lindholm@oss.qualcomm.com>
Date: Thu, Jan 9, 2025, 12:02 AM
Subject: Re: [edk2-devel] Expansion of ARCH in .dsc files
To: "Gerd Hoffmann"<kraxel@redhat.com>
Cc: <devel@edk2.groups.io>, "Ajan Zhong"<ajan.zhong@newfw.com>, "Ard Biesheuvel"<ardb+tianocore@kernel.org>, "Kinney, Michael D"<michael.d.kinney@intel.com>, "Michael Kubacki"<mikuback@linux.microsoft.com>
On Wed, 8 Jan 2025 at 15:01, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > Because "the list of all architectures being built simultaneously"
> > simply isn't very useful information build-time.
>
> I think this is not intended for building all archs in simultaneously
> (even though that often works too), but for firmware images using code
> from multiple architectures.  That is (or used to be?) common in the x86
> world, where firmware can run the PEI phase in 32-bit mode (aka IA32)
> and the DXE phase in 64-bit mode (aka X64).
>
> See OvmfPkg/OvmfPkgIa32X64.dsc

Yes, indeed.
It feels like a bit of a hack introduced specifically for that
specific case (but not documented as such).

So, Ajan - I guess that means arguably the CI job should be reworked
to call the different arch builds independently. Then the problem
would go away even without the Defines.$ARCH change.

/
    Leif
_._,_._,_

Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#121002) | | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [rebecca@openfw.io]

_._,_._,_