From: Dennis Luehring (dl.soluz_at_[hidden])
Date: 2020-08-12 08:30:08
small test with 1.74-beta looks better
does compile without a problem with current 1.74-beta
but now the linker is telling me that i need to have a clangw10 build of
lld-link : error : could not open
'libboost_serialization-clangw10-mt-gd-x32-1_74.lib': no such file or
the nature of clang-cl is a easy binary and feature compatible drop in
replacement for the microsoft-cl
until 1.74 there was no need to prepare a descent build of boost for clang
i switch multiple times per day between microsoft-cl and clang-cl
(because clang-cl gives better diagnostics)
this switching works with all (~10-20 libs) of my non-boost third party
libs without the need for a descent build - why do boost
need that?, or did i configure something wrong?
Am 11.08.2020 um 21:51 schrieb Andrey Semashev via Boost:
> On 2020-08-11 18:24, Dennis Luehring via Boost wrote:
> > some of my project using boost building with clang-cl but there are
> > still some libraries that don't
> > is there any official interest in supporting clang-cl or is it up to a
> > library maintainer to support it?
> There are no official testers running clang-cl, as far as I can see:
> However, CI configs for many libraries do include clang-cl jobs. So the
> support is each library maintainer's initiative.
> You can try filing PRs improving support for clang-cl to given libraries.
> Older versions of clang-cl were too broken to be supported, so don't
> expect those to work. And probably don't bother creating PRs adding
> workarounds for them. Newer versions seem to be better, though.
> > https://github.com/boostorg/thread/issues/286
> > "clang-cl defines _MSC_VER by ms-compatibility but BOOST_MSVC will not
> > be set." still a problem?
> BOOST_MSVC is not supposed to be defined for clang-cl.
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk