From: "Michael Brown" <mcb30@ipxe.org>
To: devel@edk2.groups.io, kraxel@redhat.com,
Ard Biesheuvel <ardb@kernel.org>
Cc: Michael Kubacki <mikuback@linux.microsoft.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Michael Kinney <michael.d.kinney@intel.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Oliver Steffen <osteffen@redhat.com>
Subject: Re: [edk2-devel] arm64 support for stuart
Date: Wed, 25 Jan 2023 17:52:36 +0000 [thread overview]
Message-ID: <01020185ea0f6992-77d208ac-1924-41fd-9d53-e0274d16291a-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <20230125165556.tvp7cgjsj2kie7b6@sirius.home.kraxel.org>
On 25/01/2023 16:55, Gerd Hoffmann wrote:
>> iasl is a different matter, as we need it to build for arm64 as well.
>> iasl is already available in the arm64 distros, so as I see it, there
>> are 3 options here:
>> - build iasl for Linux/arm64 and add it to the nuget repo
>> - allow a fallback to system-wide iasl (how?)
>
> Just use the system-wide tools is the best option IMHO. The packages
> are available in Fedora (other distros should be have them too), on both
> x86_64 and aarch64, we only need to add them to the CI container image.
> So why bother adding nuget builds?
I totally agree with this. Life is much easier when everything just
uses the existing system-wide tools.
Deliberately imposing a restriction that CI uses only system-wide tools
also helps to prevent a project slipping down into the abyss of obscure
dependencies and multi-GB custom SDK container images.
Thanks,
Michael
next prev parent reply other threads:[~2023-01-25 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 14:32 arm64 support for stuart Ard Biesheuvel
2023-01-25 16:55 ` Gerd Hoffmann
2023-01-25 17:52 ` Michael Brown [this message]
2023-01-25 18:04 ` Oliver Steffen
2023-01-25 18:27 ` Oliver Steffen
2023-01-25 19:00 ` [edk2-devel] " Michael D Kinney
2023-01-25 20:21 ` Oliver Steffen
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=01020185ea0f6992-77d208ac-1924-41fd-9d53-e0274d16291a-000000@eu-west-1.amazonses.com \
--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