Terje Mathisen wrote:
You can use the ports/winnt/vs2015 solution & project files with VS 2022. One way is to allow VS to convert the project files upon opening, but that will expose issues with 4.2.8p15 on the newer compiler (which have fixes staged for p16).Dave Hart wrote:I'm using 2022 here, would love to be able to use this version and not have to install a previous iteration.Incidentally, the Visual Studio 2015 tools and SDK can be used with VS2022 by adding the right optional components. Those are the last tools that support targeting Windows XP, VS2019 and later only support building for Windows Vista and later.
A better way is to install the VS 2015 toolchain in VS 2022. Use the VS Installer to add (under individual components, compilers, build tools and runtimes):
MSVC v140 - VS 2015 C++ build tools (v14.00) C++ Windows XP Support for VS 2017 (v141) tools [Deprecated]Then when you open ports/winnt/vs2015/ntp.sln the first time, hit cancel when offered the chance to retarget (convert) to the newer toolchain. You should then be able to build everything as-is.
-- Cheers, Dave Hart -- This is hackers@xxxxxxxxxxxxx Subscribe: hackers+subscribe@xxxxxxxxxxxxx Unsubscribe: hackers+unsubscribe@xxxxxxxxxxxxx