public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ajan Zhong" <ajan.zhong@newfw.com>
To: "Leif Lindholm" <leif.lindholm@oss.qualcomm.com>
Cc: "Gerd Hoffmann" <kraxel@redhat.com>, <devel@edk2.groups.io>,
	 "Ard Biesheuvel" <ardb+tianocore@kernel.org>,
	 "Kinney,  Michael D" <michael.d.kinney@intel.com>,
	 "Michael Kubacki" <mikuback@linux.microsoft.com>
Subject: Re: [edk2-devel] Expansion of ARCH in .dsc files
Date: Thu, 09 Jan 2025 13:14:49 +0800	[thread overview]
Message-ID: <94ba23fe064f2d82b913d4850e73e1d7918b1915.ba2fbd0b.3108.484f.a792.3519856c7a33@feishu.cn> (raw)
In-Reply-To: <CAD=n3R2fSm5byjdpBGZKHmZkVbPi6kw5S++eL3vuEMUz8=jsnQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]

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): https://edk2.groups.io/g/devel/message/121002
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]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 7326 bytes --]

  reply	other threads:[~2025-01-15 18:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 19:04 [edk2-devel] Expansion of ARCH in .dsc files Leif Lindholm via groups.io
2025-01-07 19:43 ` Joey Vagedes via groups.io
2025-01-07 20:14   ` Leif Lindholm via groups.io
2025-01-08  7:29     ` Ajan Zhong
2025-01-08 10:26       ` Ajan Zhong
2025-01-08 15:01 ` Gerd Hoffmann via groups.io
2025-01-08 16:01   ` Leif Lindholm via groups.io
2025-01-09  5:14     ` Ajan Zhong [this message]
2025-01-09 13:37     ` Ajan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=94ba23fe064f2d82b913d4850e73e1d7918b1915.ba2fbd0b.3108.484f.a792.3519856c7a33@feishu.cn \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox