Re: [Boost-build] Clang windows toolset

Subject: Re: [Boost-build] Clang windows toolset
From: Edward Diener (eldiener_at_[hidden])
Date: 2013-10-24 04:37:07

On 10/24/2013 12:26 AM, tr1gun wrote:
> On 24.10.2013 00:29, Edward Diener wrote:
>> On 10/23/2013 4:54 PM, tr1gun wrote:
>>> Hello,
>>>
>>> attached you find a patch to add the clang toolset for windows.
>>>
>>> clang_win.patch : adds the clang win toolset and passes the Z7 flag to
>>> the compiler. I think this version should be applied as clang developers
>>> strive to be compatible with msvc. To workaround the Z7 bug someone can
>>> pass at the command line: debug-store=database
>>>
>>> clang_win_ignore_z7.patch : Only filters the debug-store<object> / Z7
>>> command line. Probably not needed.
>>>
>>> common_clang_win.patch : add the clang-win name for mangling. I also
>>> included the visual studio version.  I think it should not be left out
>>> like with the intel compiler. In the end it generates the toolset name
>>> with e.g. clang 3.4 and visual stuadio 2010: clang-win3_4_vc10
>>>
>>> There are two options to setup the toolset in user-confing.jam:
>>> 1. if clang-cl is found in path:
>>> using clang : 3.4 : : <compatibility>vc10
>>>
>>> 2. Full command line for clang-cl:
>>> using clang : 3.4 : C:\MyInstallationPath\clang-cl.exe :
>>> <compatibility>vc10 ;
>>>
>>> Hope this helps to test boost with the clang toolset.
>>> At the moment it relies on the VS*COMNTOOLS variable to look up the
>>> vcvarsall.bat file. I haven't figured out how to extract the path from
>>> the msvc.jam file. Perhaps someone else can help with it.
>>> Also the auto-link header need to be changed. I can provide a patch for
>>> it when it is clear how the boost libs will be named. This depends if
>>> the visual studio version is included or not in the library name.
>>
>> To what on the latest 'trunk' are these patches supposed to be applied ?
>>
>>
>
> I did it against a snapshot of the git develop version.
> I should be applied in tools/build/v2 . I can try to create a patch
> against a svn trunk checkout if it's needed.

At this stage it really should be against svn trunk at tools/build/v2. 
Until the Git conversion is officially done and Boost developers have 
moved to Git, please consider that svn trunk is still always the latest 
version of Boost. With that said I will try it against svn trunk.

Thanks very much for working on this.