[INFO] Deprecating Windows XP Support #82
Labels
Comments
N-SPC700
added
Windows XP
|
I plan to create a Windows XP branch or fork, and cherry-pick fixes for critical issues like module corruption due to missing fsync, and republish Appveyor builds as binary releases. I do not plan to cherry-pick feature additions. The main repository may stop compiling with v141_xp (VS2017 compiler in Windows XP mode) at some point in the future. Is there a plan to switch to the v142 compiler and Windows 10 SDK? |
Gumball2415
added a commit
that referenced
this issue
Sep 5, 2021
Due to updates to Visual Studio, Dn-FamiTracker will be dropping support for Windows XP in the upcoming release. This effectively renders all versions 0.3.1.0 and below as legacy compatible versions. When these builds become obsolete, they will become deprecated and any bugs found in these builds will not get fixed unless it also affects all later builds. This new project configuration will use the v142 compiler and Windows SDK version 10.0.18362.0. Fixes #82.
Gumball2415
added a commit
that referenced
this issue
Sep 5, 2021
Due to updates to Visual Studio, Dn-FamiTracker will be dropping support for Windows XP in the upcoming release. This effectively renders all versions 0.3.1.0 and below as legacy compatible versions. When these builds become obsolete, they will become deprecated and any bugs found in these builds will not get fixed unless it also affects all later builds. This new project configuration will use the v142 compiler and Windows SDK version 10.0.18362.0. Fixes #82.
Gumball2415
added a commit
that referenced
this issue
Sep 6, 2021
Due to updates to Visual Studio, Dn-FamiTracker will be dropping support for Windows XP in the upcoming release. This effectively renders all versions 0.3.1.0 and below as legacy compatible versions. When these builds become obsolete, they will become deprecated and any bugs found in these builds will not get fixed unless it also affects all later builds. This new project configuration will use the v142 compiler and Windows SDK version 10.0.18362.0. Fixes #82.
Gumball2415
added a commit
that referenced
this issue
Sep 7, 2021
Due to updates to Visual Studio, Dn-FamiTracker will be dropping support for Windows XP in the upcoming release. This effectively renders all versions 0.3.1.0 and below as legacy compatible versions. When these builds become obsolete, they will become deprecated and any bugs found in these builds will not get fixed unless it also affects all later builds. This new project configuration will use the v142 compiler and Windows SDK version 10.0.18362.0. Fixes #82.
nyanpasu64
pushed a commit
to nyanpasu64/Dn-FamiTracker
that referenced
this issue
Sep 10, 2021
Due to updates to Visual Studio, Dn-FamiTracker will be dropping support for Windows XP in the upcoming release. This effectively renders all versions 0.3.1.0 and below as legacy compatible versions. When these builds become obsolete, they will become deprecated and any bugs found in these builds will not get fixed unless it also affects all later builds. This new project configuration will use the v142 compiler and Windows SDK version 10.0.18362.0. Fixes Dn-Programming-Core-Management#82.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to updates to Visual Code 2019, Dn-FamiTracker will be dropping Windows XP support for all new releases of Dn-FamiTracker.
While this may be sad to hear for some, we really can't keep supporting a deprecated operating system that is 7 years past it's extended support lifespan.
Despite this, the latest version as of writing (release 0.3.1.0) still supports XP. Consider this build the "legacy" compatible build for older systems. With the release of the next Dn version, 0.3.1.0 will be effectively "legacy" and/or deprecated. When 0.3.1.0 becomes obsolete, it too will become deprecated, and any bugs in that build will not get fixed unless it also affects all later builds of Dn-FamiTracker.
The text was updated successfully, but these errors were encountered: