Re: [Boost-build] Specifying toolset with different address-model

Subject: Re: [Boost-build] Specifying toolset with different address-model
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2015-06-24 14:22:47

On Wed, Jun 24, 2015 at 1:13 PM, Edward Diener <eldiener_at_[hidden]>
wrote:

> On 6/24/2015 10:51 AM, Ryan Gonzalez wrote:
>
>>
>>
>> On June 23, 2015 11:20:41 PM CDT, Edward Diener <eldiener_at_[hidden]>
>> wrote:
>>
>>> Given compiler XXX, version n.n.n, which has a different executable
>>> path
>>> depending on whether it is the 32-bit or 64-bit compiler ( this is the
>>> case for mingw-64 distros ), how do I specify separate 'using' toolsets
>>>
>>> statements in my user-config.jam for each path ?
>>>
>>> using gcc : 5.1 : path-to-32bit-version-of-compiler/g++ ;
>>> using gcc : 5.1 : path-to-64bit-version-of-compiler/g++ ;
>>>
>>> but now I have duplicate 'using' statements for the same
>>> compiler/version so that if I invoke:
>>>
>>> b2 toolset=gcc-5.1 address-model=32 ( or address-model=64 )
>>>
>>> it is impossible to distinguish between the two gcc-5.1 toolsets.
>>>
>>
>> I think you can do something like:
>>
>> using gcc : 5.1-x86 : path-to-32-bit-version ;
>> using gcc : 5.1-x64 : path-to-64-bit-version ;
>>
>
> That did not work at all.
>
> Whether I invoke:
>
> b2 toolset=gcc-5.1
>
> or
>
> b2 toolset=gcc-5.1-x86
>
> I receive the Boost Build mnessage:
>
> error: "5.1" is not a known subfeature value of <toolset>gcc

It's because dash ("-") is treated as a feature separator. You need to us
something other than dash. Commonly we use tilde ("~") in that situation.
For example:

using gcc : 5.1~x86 : path-to-32-bit-version ;
using gcc : 5.1~x64 : path-to-64-bit-version ;

-- 
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail