Re: BBv2: one library, two compilers (win: cl, icl)

From: David Abrahams (gclbb-jamboost_at_[hidden])
Date: 2003-09-04 12:30:54

Vladimir Prus <ghost_at_[hidden]> writes:

> Chris Drexler wrote:
>> I'd like to make a library where a few source files can only be
>> compiled with the intel icl compiler, the rest must be compiled
>> with cl from visual studio. I'm using Boost.Build V2 M6.
>>
>> Two questions:
>>
>> 1. Is there an easy way to use the icl enstead of cl.
>> (I couldn't find a configuration option in BBv2 to
>> switch from cl to icl)
>> 2. How can I tell the build system to use icl for
>> certain file?
>
> Hi Chris,
> sorry for somewhat delayed reply.
>
> I think it's possible to achieve what you want. In V2, intel is considered 
> just a variant of msvc compiler. I've added the following to my 
> user-config.jam:
>
> using msvc : 6.0 : "P:/Program Files/Microsoft Visual Studio/vc98" : : 
> vcvars32-p.bat ;
> using msvc : intel : "P:/Program Files/Something" : : vcvars32-p.bat icl ;
>
> And then wrote the following Jamfile.
>
> exe a : a.cpp b ;
> obj b : b.cpp : <toolset-msvc:version>intel ;
>
> which tells that 'b.cpp' should be compiled with specific version. I've tried 
> "bjam -n" and the commands look ok: i.e. there's "icl" in one of the compile 
> commands. Alas, as you've probably guesses, icl path above is bogus, since I 
> don't have it installed, so I'm not 100% it will work. If you could try it, 
> it would be great.
>
> This works only with a minor bugfix I've just made, so you'd need to get 
> updated new/property.jam, e.g. from
>
> http://zigzag.cs.msu.su:7813/~ghost/working_copy/new 
>
> or from the mirror at 
>
> http://www.boost-consulting.com/boost/tools/build/new 

That's not the way I intended for intel support to work, though it
seems to be a decent stopgap measure. intel is supposed to be a
vendor variant, so that we can have an intel.jam toolset which
inherits from msvc and sets the vendor.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com