Boost logo

Boost :

Subject: Re: [boost] clang-win, again
From: Edward Diener (eldiener_at_[hidden])
Date: 2018-10-30 00:01:21


On 10/27/2018 8:09 PM, Peter Dimov via Boost wrote:
> Egor Pugin wrote:
>
>> https://pastebin.com/kdthbdWY
>
>    clang-win.compile.asm
> bin.v2\libs\context\build\clang-vc14.1-win-cl6\...
>
> The `clang-vc14.1-win-cl6` part indicates to me that you have something
> in your user-config.
>
> When I issue
>
>    b2 --debug-clang-configuration --with-context toolset=clang-win
>
> without having any `using clang` statements in user-config, I get
> diagnostic output of the form...
>
> well, to be frank, I got
>
>    C:/boost-git/develop/tools/build/src/tools\clang-win.jam:52: in
> clang-win.init from module clang-win
>    error: Please set <compatibility> property for visual studio version!
>
> because I had reset my clang-win.jam to the develop one, but when I
> switch tools/build to pr/fix-clang-win, I get...
>
> well, I got
>
>    C:/boost-git/develop/tools/build/src/tools\clang-win.jam:71: in
> clang-win.init from module clang-win
>    error: Cannot configure toolset clang-win: no 'clang-cl.exe' command
> found or given
>
> because I forgot to add llvm to the PATH, but when I do that, I get (and
> this time it will work, I promise)
>
> notice: [clang-win] configuring 'clang-cl.exe' version '6.0.1'
> notice: [clang-win] 32: using assembler '"C:\\Program Files
> (x86)\\Microsoft Vis
> ual
> Studio\\2017\\Community\\VC\\Tools\\MSVC\\14.15.26726\\bin\\HostX64\\x86\ml.
>
> exe"'
> notice: [clang-win] 32: using archiver '"C:\\Program Files
> (x86)\\Microsoft Visu
> al
> Studio\\2017\\Community\\VC\\Tools\\MSVC\\14.15.26726\\bin\HostX86\x86\link.e
>
> xe" /lib'
> notice: [clang-win] 32: using SDK path 'C:\\Program Files (x86)\\Windows
> Kits\\1
> 0\\bin\x86'
> notice: [clang-win] 32: using manifest-tool '"C:\\Program Files
> (x86)\\Windows K
> its\\10\\bin\x86\mt.exe"'
> notice: [clang-win] 32: using resource-compiler '"C:\\Program Files
> (x86)\\Windo
> ws Kits\\10\\bin\x86\rc.exe"'
> notice: [clang-win] 32: using mc-compiler '"C:\\Program Files
> (x86)\\Windows Kit
> s\\10\\bin\x86\mc.exe"'
> notice: [clang-win] 32: using idl-compiler '"C:\\Program Files
> (x86)\\Windows Ki
> ts\\10\\bin\x86\midl.exe"'
> notice: [clang-win] 64: using assembler '"C:\\Program Files
> (x86)\\Microsoft Vis
> ual
> Studio\\2017\\Community\\VC\\Tools\\MSVC\\14.15.26726\\bin\\HostX64\\x64\ml6
>
> 4.exe"'
> notice: [clang-win] 64: using archiver '"C:\\Program Files
> (x86)\\Microsoft Visu
> al
> Studio\\2017\\Community\\VC\\Tools\\MSVC\\14.15.26726\\bin\\HostX64\\x64\\lin
>
> k.exe" /lib'
> notice: [clang-win] 64: using SDK path 'C:\\Program Files (x86)\\Windows
> Kits\\1
> 0\\bin\x64'
> notice: [clang-win] 64: using manifest-tool '"C:\\Program Files
> (x86)\\Windows K
> its\\10\\bin\x64\mt.exe"'
> notice: [clang-win] 64: using resource-compiler '"C:\\Program Files
> (x86)\\Windo
> ws Kits\\10\\bin\x64\rc.exe"'
> notice: [clang-win] 64: using mc-compiler '"C:\\Program Files
> (x86)\\Windows Kit
> s\\10\\bin\x64\mc.exe"'
> notice: [clang-win] 64: using idl-compiler '"C:\\Program Files
> (x86)\\Windows Ki
> ts\\10\\bin\x64\midl.exe"'
> Performing configuration checks
>
> and so on, with the directory of the intermediate files being
> clang-win-6.0.1, which matches my LLVM version.
I have merged Peter's fix for clang-win.jam, from a PR he created, to
Boost Build's 'develop' branch. Thanks, Peter, for working on this !
This will make it easier for others who participated on this thread to
try his update.


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk