thank for clearing that up - two times :) last question: what is the reason for not setting BOOST_MSVC and BOOST_LIB_TOOLSET if _MSC_VER && __clang__ is set? this way clang-cl could really work as a drop in replacement for microsoft-cl without changing anything in the project are there just too many bugs with clang-cl's microsoft compatiblity or is the microsoft-cl and clang-cl version mapping problematic (which version of clang-cl is compatible enough with what version of mircosoft-cl?) Am 12.08.2020 um 20:28 schrieb Peter Dimov via Boost:
Dennis Luehring wrote:
Boost 1.69
microsoft-cl
1>------ Rebuild All started: Project: clang_cl_tests, Configuration: Debug Win32 ------ 1>clang_cl_tests.cpp 1>Linking to lib file: libboost_regex-vc141-mt-gd-x32-1_69.lib 1>Linking to lib file: libboost_regex-vc141-mt-gd-x32-1_69.lib 1>_MSC_VER=1916
...
clang-cl
1>------ Rebuild All started: Project: clang_cl_tests, Configuration: Debug Win32 ------ 1>clang_cl_tests.cpp(12): warning : _MSC_VER=1916 [-W#pragma-messages]
Yes, as I said, Clang doesn't autolink at all in 1.69. Autolink for Clang was enabled in 1.71.
https://github.com/boostorg/config/commit/a18911902dff03f37582696a13bf60768c...
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost