Re: [boost] clang-win, again

Subject: Re: [boost] clang-win, again
From: Edward Diener (eldiener_at_[hidden])
Date: 2018-08-12 01:52:09

On 8/11/2018 9:12 PM, Peter Dimov via Boost wrote:
> Edward Diener wrote:
>> On 8/11/2018 6:22 PM, Peter Dimov via Boost wrote:
>> > Has anyone succeeded in getting clang-cl.exe working under b2? I've 
>> > installed llvm-6.0.1, added it to PATH, put
>> >
>> >Â Â Â Â  using clang-win : : : <compatibility>vc14 ;
>>
>> I use this:
>>
>> using clang : 6.0cl : C:/Utilities/LLVM/601/x32/bin/clang++
>> Â  :
>> Â  <cxxflags>-fmacro-backtrace-limit=0
>> Â  <cxxflags>-Wno-invalid-token-paste
>> Â  <compileflags>-fmsc-version=1900
>> Â  <compileflags>--target=i686-pc-windows-msvc
>> Â  <linkflags>--target=i686-pc-windows-msvc
>> Â  <linkflags>-fuse-ld=lld
>> Â  ;
> 
> This kind of works, even without the options, using just the simple
> 
>  Â Â  using clang ;
> 
> and without setting up any MSVC build environment. clang++ finds MSVC 
> 2017 on its own.
> 
> But unfortunately any dynamic_cast use fails with
> 
>  Â Â  undefined symbol: __imp___RTDynamicCast
> 
> regardless of whether I use -fuse-ld=lld. :-/

I agree. It is not very good. In general clang under Windows, whether 
using gcc or vc++ has many problems, but almost always with the linker 
and rarely with the compiler, although it still can not handle VMD with 
its preprocessor. I gave up trying to get the clang developers to pay 
any attention to any of this a while ago.