public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann via groups.io" <kraxel=redhat.com@groups.io>
To: devel@edk2.groups.io, leif.lindholm@oss.qualcomm.com
Cc: Ajan Zhong <ajan.zhong@newfw.com>,
	 Ard Biesheuvel <ardb+tianocore@kernel.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Expansion of ARCH in .dsc files
Date: Wed, 8 Jan 2025 16:01:21 +0100	[thread overview]
Message-ID: <2nvp477n4ah4o4tlbw5h3a5tsrrzfbzfmdoeqw2cpmygxzsnhl@3swp7whktlfu> (raw)
In-Reply-To: <CAD=n3R2V1_KGrZzDKqXSukiinmyqEJAL6TNSGGoEK48_RVm7dA@mail.gmail.com>

  Hi,

> 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

take care,
  Gerd



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120972): https://edk2.groups.io/g/devel/message/120972
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]
-=-=-=-=-=-=-=-=-=-=-=-



  parent reply	other threads:[~2025-01-08 15:01 UTC|newest]

Thread overview: 5+ 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 15:01 ` Gerd Hoffmann via groups.io [this message]
2025-01-08 16:01   ` Leif Lindholm via groups.io

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=2nvp477n4ah4o4tlbw5h3a5tsrrzfbzfmdoeqw2cpmygxzsnhl@3swp7whktlfu \
    --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