FYI: recent VS2022 17.10.x gives "Boost toolset is unknown (compiler MSVC 19.40.33808.0)" warning - due to Microsoft changing of the toolset version
...using Boost only CMake configure The MSVC toolset will increment its minor version number from|19.39|(VS 2022 v17.9) to|19.40|(VS 2022 v17.10). https://devblogs.microsoft.com/cppblog/msvc-toolset-minor-version-number-14-... is still useable - did not check if building boost is a problem
Dennis Luehring wrote:
...using Boost only CMake configure
The MSVC toolset will increment its minor version number from|19.39|(VS 2022 v17.9) to|19.40|(VS 2022 v17.10).
https://devblogs.microsoft.com/cppblog/msvc-toolset-minor-version- number-14-40-in-vs-2022-v17-10/
is still useable - did not check if building boost is a problem
Thanks, should be fixed by https://github.com/boostorg/boost_install/commit/3f67136ec1e7855f29c40db8949... The CMake build also deduces the wrong toolset (vc144), will take care of it as well.
The CMake build also deduces the wrong toolset (vc144), will take care of it as well.
what is the effect - im currently bound to 1.84 - what toolset is then used for building? Am 21.06.2024 um 13:24 schrieb Peter Dimov via Boost:
Dennis Luehring wrote:
...using Boost only CMake configure
The MSVC toolset will increment its minor version number from|19.39|(VS 2022 v17.9) to|19.40|(VS 2022 v17.10).
https://devblogs.microsoft.com/cppblog/msvc-toolset-minor-version- number-14-40-in-vs-2022-v17-10/
is still useable - did not check if building boost is a problem
Thanks, should be fixed by
https://github.com/boostorg/boost_install/commit/3f67136ec1e7855f29c40db8949...
The CMake build also deduces the wrong toolset (vc144), will take care of it as well.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Dennis Luehring wrote:
The CMake build also deduces the wrong toolset (vc144), will take care of it as well.
what is the effect - im currently bound to 1.84 - what toolset is then used for building?
The libraries are named e.g. libboost_atomic-vc144-mt-gd-x64-1_86.lib instead of the correct libboost_atomic-vc143-mt-gd-x64-1_86.lib I don't think there's any other effect. The fix for that is https://github.com/boostorg/cmake/commit/ae2e6a647187246d6009f80b56ba4c2c8f3...
participants (2)
-
Dennis Luehring -
Peter Dimov