Re: using clang-cl with 1.74-rc2 forces auto-link to search for clangw10 libs instead of using existing Microsoft-cl built libs

From: pbristow_at_[hidden]
Date: 2020-08-12 16:17:01

> -----Original Message-----
> From: Boost <boost-bounces_at_[hidden]> On Behalf Of Dennis Luehring via Boost
> Sent: 12 August 2020 14:59
> To: boost_at_[hidden]
> Cc: Dennis Luehring <dl.soluz_at_[hidden]>
> Subject: [boost] using clang-cl with 1.74-rc2 forces auto-link to search for clangw10 libs instead of using
> existing microsoft-cl built libs
> 
> using latest VS2010 and llvm/clang 10.0.0 release (10.0.1 is a litte bit more recent but no windows builds
> available)

Aside: WinLibs standalone build of GCC and MinGW-w64 for Windows at Winlibs.com has very recent builds, mainly intended for Mingw-64, but often OK for Windows clang-cl too?

(I am using Clang and GCC from this site with CodeBlocks IDE and also using b2/bjam but I could not get the clang-win .exe to build reliably and am using clang-linux .exe in my user-config.jam. However this isn't any help to your difficulties ☹ ).

> compiler set to 2017 microsoft-cl in VS2017:
> libboost_serialization-vc141-mt-gd-x32-1_74.lib
> 
> compiler set to clang-cl in VS2017:
> libboost_serialization-clangw10-mt-gd-x32-1_74.lib
> 
> that behavior is new to 1.74 - older boosts versions 1.69..1.73 would use the vc141 libs what makes
> sense because clang-cl is the microsoft-cl compatible replacement
> 
> normaly there is no need to switch any external libs when using clang-cl instead of microsoft-cl