From: "Sean" <spbrogan@outlook.com>
To: "discuss@edk2.groups.io" <discuss@edk2.groups.io>,
"rebecca@bsdio.com" <rebecca@bsdio.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Liming Gao <gaoliming@byosoft.com.cn>,
Michael D Kinney <michael.d.kinney@intel.com>,
Oliver Smith-Denny <osde@linux.microsoft.com>
Subject: Re: [edk2-devel] [edk2-discuss] Removal of VS2015 (and maybe VS2017) and deprecated toolchains (GCC48, GCC49, GCC5)
Date: Tue, 22 Oct 2024 15:53:44 +0000 [thread overview]
Message-ID: <CH3P221MB1368DDC450B8874F010BB3C7C84C2@CH3P221MB1368.NAMP221.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <1ed98fbf-7799-4391-aa8e-337e8cc5e5c7@bsdio.com>
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
I support removal of vs2015 and 2017. Since ci only builds and tests n (vs2022). Supporting n-1 (vs2019) is already just on faith and with the idea that reported failures will be fixed.
I also agree with dropping previously deprecated tags. Thanks for the effort.
Thanks
Sean
________________________________
From: discuss@edk2.groups.io <discuss@edk2.groups.io> on behalf of Rebecca Cran <rebecca@bsdio.com>
Sent: Tuesday, October 22, 2024 4:18:51 AM
To: devel@edk2.groups.io <devel@edk2.groups.io>; discuss@edk2.groups.io <discuss@edk2.groups.io>
Cc: Liming Gao <gaoliming@byosoft.com.cn>; Michael D Kinney <michael.d.kinney@intel.com>; Oliver Smith-Denny <osde@linux.microsoft.com>
Subject: [edk2-discuss] Removal of VS2015 (and maybe VS2017) and deprecated toolchains (GCC48, GCC49, GCC5)
With the addition of VS2022 I'd like to propose removing VS2015, and
discuss whether people think it might be suitable to also remove VS2017
too, from tools_def.txt.
Back in July, Oliver sent the following message:
"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."
In addition, since GCC48, GCC49 and GCC5 have been marked deprecated for
over a year, I'd like to proceed with removing them as well.
Please provide feedback by Thursday October 31st. In the absence of
feedback I'll plan to proceed with removing VS2015, GCC48, GCC49 and GCC5.
--
Rebecca Cran
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120650): https://edk2.groups.io/g/devel/message/120650
Mute This Topic: https://groups.io/mt/109154422/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 3433 bytes --]
next prev parent reply other threads:[~2024-10-22 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 11:18 [edk2-devel] Removal of VS2015 (and maybe VS2017) and deprecated toolchains (GCC48, GCC49, GCC5) Rebecca Cran
2024-10-22 12:14 ` Leif Lindholm via groups.io
2024-10-24 3:23 ` Michael D Kinney
2024-10-24 5:14 ` Rebecca Cran
2024-10-22 15:53 ` Sean [this message]
2024-10-22 17:38 ` [edk2-devel] [edk2-discuss] " Michael D Kinney
2024-10-22 23:16 ` Rebecca Cran
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=CH3P221MB1368DDC450B8874F010BB3C7C84C2@CH3P221MB1368.NAMP221.PROD.OUTLOOK.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