Re: current situation with clang-cl?

From: Dennis Luehring (dl.soluz_at_[hidden])
Date: 2020-08-12 14:17:17

>Looking at the history of boost/config/auto_link.hpp,
>1.70 didn't autolink under Clang at all

>and since 1.71 Clang autolinks to clangw libraries.
>So I don't see why 1.73 and 1.74 would differ.

Clang or Clang-cl?

a freshly build 1.73 and 1.74-rc2 showing exact that
behavior

both boost versions are only build with vc141 - there are only vc141 libs available

if using boost 1.73 it makes no difference in building with microsoft-cl or clang-cl

if using boost 1.74 - boost will ask for clangw10 libs

Am 12.08.2020 um 16:08 schrieb Peter Dimov via Boost:
> Dennis Luehring wrote:
>
> > until 1.74 there was no need to prepare a descent build of boost for clang
>
> Looking at the history of boost/config/auto_link.hpp, 1.70 didn't autolink
> under Clang at all, and since 1.71 Clang autolinks to clangw libraries. So I
> don't see why 1.73 and 1.74 would differ.
>
> If you want to override this, #define BOOST_LIB_TOOLSET to vc141 (if using
> 2017.)
>
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost