public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Andrew Fish" <afish@apple.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
	Laszlo Ersek <lersek@redhat.com>
Cc: Rebecca Cran <rebecca@bsdio.com>,
	Mike Kinney <michael.d.kinney@intel.com>,
	Rebecca Cran <rebecca@nuviainc.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>,
	Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] Build fails with VS2012
Date: Tue, 11 May 2021 17:04:35 -0700	[thread overview]
Message-ID: <5E80F8EB-C736-4E53-9AAB-12F4C064CA58@apple.com> (raw)
In-Reply-To: <2788c447-7fda-fe7b-a5fe-f9c60fa0cb89@redhat.com>

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

I’m always happy to resolve any Xcode issues. 

Thanks,

Andrew Fish

> On May 11, 2021, at 7:41 AM, Laszlo Ersek <lersek@redhat.com> wrote:
> 
> On 05/11/21 02:14, Rebecca Cran wrote:
>> Thanks. The obvious toolchains that are missing from ReadMe.rst are any
>> versions of XCODE and CLANG.
>> Also, it might be nice to specify _which_ GCC5 versions are supported,
>> since that covers gcc 5 through 11 and gcc 5.x currently causes a build
>> error. We maybe only care about gcc 7 and newer these days?
>> 
>> I just tried building with VS2015 and VS2013, and there was a build
>> error because it seems the location of rc.exe has changed. After fixing
>> that they successfully built OVMF. But it sounds like we possibly only
>> want to make sure that VS2017 and VS2019 are kept working now.
>> 
>> I've cc'd Bret and Sean because I'm wondering if there are plans to add
>> more toolchain/OS combinations into the GitHub/Azure solution? For
>> example adding macOS with XCODE5? Also, how about post-commit or nightly
>> builds that run more extensive tests, possibly generating binaries for
>> OVMF that people can try without building it themselves? Or would that
>> be something that might be useful for me to implement as a third-party
>> solution?
>> 
> 
> Too many good questions!
> 
> Personally, I care for gcc-8, and later.
> 
> Thanks
> Laszlo
> 
> 
> 
> 


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

  reply	other threads:[~2021-05-12  0:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08 19:47 Build fails with VS2012 Rebecca Cran
2021-05-10 11:56 ` [edk2-devel] " Laszlo Ersek
2021-05-10 13:20   ` Rebecca Cran
2021-05-10 23:31     ` Michael D Kinney
2021-05-11  0:14       ` Rebecca Cran
2021-05-11 14:41         ` Laszlo Ersek
2021-05-12  0:04           ` Andrew Fish [this message]
     [not found] <167D2F1936103629.17661@groups.io>
2021-05-09 17:42 ` Rebecca Cran
2021-05-10 11:59   ` Laszlo Ersek

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=5E80F8EB-C736-4E53-9AAB-12F4C064CA58@apple.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