From: "Rebecca Cran" <rebecca@bsdio.com>
To: Gerd Hoffmann <kraxel@redhat.com>, devel@edk2.groups.io
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
Sami Mujawar <sami.mujawar@arm.com>
Subject: Re: [edk2-devel] ArmPkg,ArmPlatformPkg: Adding nasm files to allow builds with VS2022
Date: Tue, 5 Nov 2024 06:55:55 -0700 [thread overview]
Message-ID: <f22ed8ba-50e7-4338-88e0-b474aea9656d@bsdio.com> (raw)
In-Reply-To: <ee6qu3nfflddfw72ehx6akoqdadnuehmbvetsbzi45c5xiaof7@4rsa5ejhv7l6>
On 11/5/24 5:58 AM, Gerd Hoffmann wrote:
> On Wed, Oct 23, 2024 at 05:48:46PM -0600, Rebecca Cran wrote:
>> I've been wondering if it might be worth adding nasm files to ArmPkg,
>> ArmPlatformPkg etc. to allow platforms to be built with VS2022 - mainly
>> because different compilers can detect different issues with the code.
> What is nasm? I suspect it is not referring to http://www.nasm.us/?
Yes, I'm referring to the assembler files used on Windows which are
built with nasm from http://www.nasm.us .
--
Rebecca
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120730): https://edk2.groups.io/g/devel/message/120730
Mute This Topic: https://groups.io/mt/109181847/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-11-05 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 23:48 [edk2-devel] ArmPkg,ArmPlatformPkg: Adding nasm files to allow builds with VS2022 Rebecca Cran
2024-10-24 9:08 ` Sami Mujawar
2024-10-24 15:48 ` Oliver Smith-Denny
2024-10-24 16:31 ` Rebecca Cran
2024-11-05 12:58 ` Gerd Hoffmann
2024-11-05 13:55 ` Rebecca Cran [this message]
2024-11-05 15:40 ` Gerd Hoffmann
2024-11-05 15:46 ` Rebecca Cran
2024-11-05 15:49 ` Oliver Smith-Denny
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=f22ed8ba-50e7-4338-88e0-b474aea9656d@bsdio.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