Using two different Visual Studio installations as generator

[bernb]

For our software, we want to set a fixed MSVC compiler version (including patch version) when building and want to build two different versions:

cmake -G "Visual Studio 17 2022" -A x64,version=10.0 -T "v143,version=14.44.35207,cuda=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.8"
cmake -G "Visual Studio 17 2022" -A x64,version=10.0 -T "v143,version=14.38.33130,cuda=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.8"

As it’s not possible to select a specific patch version via the installer, I tried to use two different Visual Studio installations. However, it seems that cmake only consider the latest installation. Is that correct or am I doing something wrong?

[Oodini]

It may be related to this problem:

Cannot set toolset when configuring with the Visual Studio 2022 generator.

I have installed on my machine Visual Studio 2022 17.9 with the MSVC toolsets 14.36, 14.38 and 14.39. I created with Visual Studio a new “CMake project” and after configuring it with cmake -S . -B build -G "Visual Studio 17 2022" I noticed that CMake is choosing MSVC 14.36; the oldest one. I tried to manually choose the latest toolset by passing -T v143,version=14.39 but every time it fails with No CMAKE_C/CXX_COMPILER could be found.. I tried the same while under the Visual Studio developer Po…

[bernb]

So cmake normally should be able to find and use msvc versions from all VS installation?
It does work for me though when I use only one VS installation. That’s unfortunately not an option, because the versions are externally fixed and differ (in their patch version) from what the VS installer provides.

[Oodini]

I do have similar troubles:

Can the VS 2019 generator be used if only VS2022 is installed?

For anyone else who finds themselves here, baffled, replace the "-G “Visual Studio 15 2017” or -G “Visual Studio 16 2019” option with -T v142. It will say “Building for: Visual Studio 17 2022” BUT when you open the .sln file it will say “Visual Studio 2019” and the toolset will be set to 2019.