Conversation
|
The specific version number(s) are needed we learned the hard way. I will try to figure out what we should use. |
|
Here's the list of toolset versions: https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B#Internal_version_numbering The latest SDK versions can be found here: https://en.wikipedia.org/wiki/Microsoft_Windows_SDK Not sure which SDK version we should target. Not sure it matters? |
|
On my system, the current toolset version is 14.44.35207. MSVC is 17.14.4. With -T v143 in configure.cmake, CSE builds successfully and appears to use 14.44.32507. If I change to -T v143,version=14.44.35207, I cmake will not configure -- If I configure with just v143 and then set by hand the MSVC Toolset Version to 14.44.35207, CSE builds OK. Google queries located various postings about MSVC bugs related to toolset selection. I did not yet fully understand whether those problems apply to our situation. |
Changed the Windows platform toolset specified in
configure.cmakefrom "Visual Studio 2019 (v142)" to "Visual Studio 2022 (v143)". Unable to identify a specific version (previously, 14.29.16.11; toolset, compiler?), as was listed previously. The output of perfmap3.cse on Win32 changed slightly (an extra "Info" message is displayed.) This version passes the CI, but now my local Mac gives several 0/-0 diffs in perfmap.cse, compared to the CI (due to AppleClang 14 vs. 15?).