This could be an additional parameter of the Kit (like "visualStudioArchitecture") but controlling the SDK version that is passed to vcvarsall.bat as its 3rd (or 2nd if no platform type is specified) argument, maybe something like "visualStudioWinSDKVersion". So at this point I might as well get rid of the MSVC specific setup (using vcvars) and create the whole environment, replicating the result of calling vcvars with the correct option.Īfter looking at this in more details, maybe I'm missing something but I've come to the conclusion that the proper way of doing this would be to pass the windows SDK version as a parameter to vcvarsall.bat as it's intended to work that way. However this seems like in internal variable, subject to change, and feels kind of hackish to me.īeing able to override the environment variables set by the script, as you mentioned, could be an idea but the SDK version is present in many variables and highly intertwined with the toolset version etc.
If one chooses, some alternatives can include MinGW or Cygwin in this tutorial instead, one recommended method of building assignments will be through the cmake-gui: CMake-gui Download, and using Visual Studios 2017, installed with Visual C++ Support.
Returning to the problem at hand, after some digging in the scripts, I found another environment variable that I could set prior to calling vcvars to control the windows SDK version: _VSCMD_ARG_WINSDK. For Windows, cmake and make compatibilities especially can be more involved, as gcc and such compilers do not come packaged with the OS. Maybe you guys have more insights into this than I do.
#Cmake windows sdk trial
I have no idea why this works in Visual Studio as this seems to be a totally undocumented and maybe unintended "feature" which I just happened to find by trial and error. Now I truly don't understand how my settings work in Visual Studio 2019 since having WindowsSDKVersion=8.1 in my CMakeSettings.json correctly sets all environment variables to the 8.1 SDK as if I'd passed the correct option to vcvars This led me to (incorrectly) believe that setting the environment variable before calling the script should work. As you said the script overrides any previously set value of WindowsSDKVersion.
#Cmake windows sdk install
I've made some more tests on my side today to better understand how the Windows SDK version can be controlled when running vcvars. There are several ways to install CMake, depending on your platform. Hi Bob, sorry for the late reply I was out-of-office last week.
0 kommentar(er)
