With Visual Studio 2022 version 17.10, Microsoft upped the minor version number of the toolset and compiler to 40 (i.e. 14.40 and 19.40, respectively), thereby breaking the assumption in OWLNext (include/private/owllink.h (sourceforge.net)) that toolset "v143" in VS 2022 would have minor version numbers restricted to 3X and _MSC_VER within 1930-1939.
See: https://devblogs.microsoft.com/cppblog/msvc-toolset-minor-version-number-14-40-in-vs-2022-v17-10/
Reported by @patbir [discussion:00960e22aa].
Discussion: 00960e22aa
Discussion: VS2022 17.10.0 and _MSC_VER >=1940
Discussion: Preparing updates for OWLNext 7.0, 6.44 and 6.36
News: 2024/05/owlnext-7014-64424-6369-updates
Wiki: OWLNext_Stable_Releases
Anonymous
This feature was implemented on the trunk in [r6979] and merged into Owlet in [r6980] and into 6.36, 6.44 and 7.0 in [r6981].
Related
Commit: [r6979]
Commit: [r6980]
Commit: [r6981]
Last edit: Vidar Hasfjord 2024-05-24
This VS versioning change is quite unfortunate, as it is not clear what the version of a future Visual C++ (2025?) would be and thus making it harder to future-proof OWLNext.
Chaning the check to
#if _MSC_VER >= 1950is good enough, we will revisit it when new versions are released.