Replies: 5 comments 2 replies
-
|
It seems reasonable to me to drop the out of support ones. I'd suggest that if possible for SCons to detect attempts to use such out of date toolchains and issue an error message stating that support has been dropped, and to include in that error message the last version of SCons which supported them. That way, if you do need for some reason to build something with an ancient toolchain and you try to use a too-new version of SCons, you don't have to go searching: it just tells you what SCons version you can downgrade to and regain support. |
Beta Was this translation helpful? Give feedback.
-
|
Probably need a deprecation cycle? |
Beta Was this translation helpful? Give feedback.
-
|
I'd argue you don't need a deprecation cycle. If you just pulled support for the no-longer-maintained VS codes right now, the next release of SCons would drop support for MS tools versions released before Oct 2013. That's almost a decade ago. And if you needed to use a ten year old toolset that has left support, that's ok - just use any older SCons release. |
Beta Was this translation helpful? Give feedback.
-
|
Also there's two ways to get a specific version of MSVC:
So we'd have to detect which one was selected by above and issue deprecation warning if in the no longer supported. Lemme float a poll on twitter/x |
Beta Was this translation helpful? Give feedback.
-
|
Maybe a middle ground? If 4.6 comes out in the next month or two, it could include in the release note that the following release (which presumably would land like March/April 2024, would no longer support msvc prior to (some-version). That's a kind of deprecation... and I guess a note in the table here: https://scons.org/doc/production/HTML/scons-man.html#cv-MSVC_VERSION |
Beta Was this translation helpful? Give feedback.
-
|
@mwichmann - that sounds workable. Next major release won't be "quick" so any users who had an issue with such would have an opportunity and notice to let us know. |
Beta Was this translation helpful? Give feedback.
-
|
Adding blurb here: The goal is not to stop supporting old versions for which we already have code (because unfortunately I've seen some really old msvc versions still in use in the wild), but rather to stop working on them as they are unlikely to change at this point. |
Beta Was this translation helpful? Give feedback.
-
Microsoft now supports "Visual Studio", including the compilers it runs, for a 10 year period, five years of full support and five years of extended support (no new features, security fixes only, etc.). Earlier on these periods were shorter. SCons has an understanding of compilers going all the way back to Visual Studio 6.0, which is out of support for nearly 20 years.
This is a prod to start a discussion whether SCons should actually clean out mention of some or all of the "out of support" versions.
Here's the product table in the same form as found on Wikipedia:
Beta Was this translation helpful? Give feedback.
All reactions