public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, michael.d.kinney@intel.com,
	"osde@linux.microsoft.com" <osde@linux.microsoft.com>,
	Rebecca Cran <rebecca@os.amperecomputing.com>
Subject: Re: [edk2-devel] Drop VS2015 Support
Date: Tue, 9 Jul 2024 15:44:49 -0600	[thread overview]
Message-ID: <8e0415c6-5b1c-40e7-be16-b80a3aac783b@bsdio.com> (raw)
In-Reply-To: <CO1PR11MB4929D19ACB274B161081C98ED2DB2@CO1PR11MB4929.namprd11.prod.outlook.com>

On 7/9/24 14:01, Michael D Kinney wrote:
> What do you mean by drop?
> 
> Remove from CI or remove from both CI and tools_def.txt?

I'm thinking remove it from both.

-- 
Rebecca Cran

> 
> Mike
> 
>> -----Original Message-----
>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Oliver Smith-
>> Denny
>> Sent: Tuesday, July 9, 2024 12:48 PM
>> To: devel@edk2.groups.io; Rebecca Cran <rebecca@os.amperecomputing.com>
>> Subject: [edk2-devel] Drop VS2015 Support
>>
>> Hi Rebecca,
>>
>> Per Liming's request I am moving this discussion to the mailing list.
>> Now that VS2022 support has been added to edk2, can we drop VS2015
>> support (honestly VS2017 could be dropped, too). This is an almost
>> 10 year old toolchain that is unsupported, has many quirks, and will
>> continue to require odd changes from new code to support it, for no
>> gain. VS2015 (and 2017) users should move to VS2022.



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119857): https://edk2.groups.io/g/devel/message/119857
Mute This Topic: https://groups.io/mt/107129562/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-07-09 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 19:47 [edk2-devel] Drop VS2015 Support Oliver Smith-Denny
2024-07-09 20:01 ` Michael D Kinney
2024-07-09 21:44   ` Rebecca Cran [this message]
2024-07-13 18:47     ` 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=8e0415c6-5b1c-40e7-be16-b80a3aac783b@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