Subject: Re: [boost] `b2 toolset=clang-win` now works on Appveyor
From: Edward Diener (eldiener_at_[hidden])
Date: 2018-11-17 19:54:14
On 11/15/2018 12:09 PM, Peter Dimov via Boost wrote:
> With the current develop branch (since Boost.Build hasn't been merged to
> master yet),
>
> Â Â b2 toolset=clang-win
>
> now works on Appveyor without additional configuration. You can see it
> in action at
>
>
> https://ci.appveyor.com/project/pdimov/assert/builds/20331077/job/0hux9a6mlr4iqvjr
If I invoke 'b2 toolset=clang-win-7.0' against some test jam file with a
user-config.jam file of 'using clang-win : 7.0 :
C:/Utilities/LLVM/700/x32/bin/clang-cl ;' everything works fine. But if
I invoke 'b2 toolset=clang-win-6.0' against some test jam file with a
user-config.jam file of 'using clang-win : 6.0 :
C:/Utilities/LLVM/601/x32/bin/clang-cl ;' I constantly get:
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\VC\Tools\MSVC\14.16.27023\include\yvals_core.h(294,5):
error: STL1000: Unexpected compiler version, expected Clang 7 or newer.
#error STL1000: Unexpected compiler version, expected Clang 7 or newer.
Even if I add a 'using msvc : 14.0 ;' to my user-config.jam the same
problem occurs. It seems as if clang-win always uses the latest version
of vc++, which of course does not work with an earlier version of clang,
as the error message shows.