Subject: Re: [boost] clang-win, again
From: Peter Dimov (lists_at_[hidden])
Date: 2018-10-27 01:24:19
> Yeah, just relying on PATH seems to work, as long as one opens the correct
> dev prompt (the 64 bit one). But that's not very satisfying.
You can try the attached clang-win.jam, with
using clang-win : : C:/llvm-6.0.1/bin/clang-cl.exe ;
in user-config, or just
using clang-win ;
if clang-cl.exe is in your PATH. This shouldn't need a developer command
It won't win any bjam toolset awards, but the old one didn't work and this
does, at least for me, so there's that.
Some libraries get confused when they see clang-win though, we have work to
do. Thread, for instance, thinks that I want to use threadapi=pthread for
some reason instead of threadapi=win32; Log fails with a link error:
object_name.obj : error LNK2019: unresolved external symbol GetUserNameExW
referenced in function "int `public: __cdecl
log::v2_mt_nt6::ipc::object_name::dtor$2::scope,char const *)'::`1'::dtor$2"
: fatal error LNK1120: 1 unresolved externals
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk