public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, osde@linux.microsoft.com,
	"Sami Mujawar" <sami.mujawar@arm.com>,
	"Leif Lindholm" <quic_llindhol@quicinc.com>
Cc: "Hemendra Dassanayake" <Hemendra.Dassanayake@arm.com>,
	"Akanksha Jain" <Akanksha.Jain2@arm.com>
Subject: Re: [edk2-devel] ArmPkg,ArmPlatformPkg: Adding nasm files to allow builds with VS2022
Date: Thu, 24 Oct 2024 10:31:39 -0600	[thread overview]
Message-ID: <de05e704-c1fd-476d-ad79-4905e134ca8a@app.fastmail.com> (raw)
In-Reply-To: <77108ccd-784b-4e13-8771-4f3110654ece@linux.microsoft.com>

Awesome, thanks!

On Thu, Oct 24, 2024, at 9:48 AM, Oliver Smith-Denny wrote:
> On 10/24/2024 2:08 AM, Sami Mujawar wrote:
>> Hi Rebecca,
>> 
>> Thank you for bringing up this topic.
>> 
>> I agree we should get Visual Studio compiler support for Arm in edk2. 
>> The Visual Studio static analysis has helped to detect issues in 
>> DynamicTablesPkg in the past (when we did not have any dependency on 
>> assembly code).
>> 
>> I can see that Visual Studio Compiler support is already available in 
>> Project Mu. Would it be good to pull in the changes from there?
>> 
>> We would need to:
>> 
>>   * look at the compatibility of the licenses.
>>   * review and align any changes with the latest edk2 code base (Note
>>     this effort would be significantly less than starting from scratch).
>> 
>> @Oliver Smith-Denny <mailto:osde@linux.microsoft.com> is this something 
>> you can help with, please?
>> 
>
> Yes, we have been wanting to upstream our ARM VS2022 build support,
> including the nasm files, but we also weren't sure what the upstream
> appetite was. I will help coordinate that from our side.
>
> License-wise, we use the same BSD-2-Clause-Patent license as edk2
> so there should be no issue.
>
> I'll deal with any changes with the latest edk2 codebase, we are
> updated to the edk2-stable202405 tag, so the delta shouldn't
> be huge.
>
> Thanks,
> Oliver
>
>
> 


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



      reply	other threads:[~2024-10-24 16:31 UTC|newest]

Thread overview: 4+ 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 [this message]

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=de05e704-c1fd-476d-ad79-4905e134ca8a@app.fastmail.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