Re: [Boost-build] cxxflags depending on tooslet and version?

Subject: Re: [Boost-build] cxxflags depending on tooslet and version?
From: Vladimir Prus (ghost_at_[hidden])
Date: 2012-03-29 14:40:47

On 29/03/12 22:32, Oliver Kowalke wrote:
> Am 29.03.2012 20:22, schrieb Steven Watanabe:
>> AMDG
>>
>> On 03/29/2012 10:10 AM, Oliver Kowalke wrote:
>>> Hmm - maybe following would be a better solution:
>>> I declare an additional property<splitstack> in my Jamfile - per
>>> default it is disabled (value 'false').
>>> If the user declares 'bjam splitstack=true' on command line - I'll
>>> define an pre-processor macro BOOST_USE_SPLITSTACK and enable code using
>>> split stacks.
>>> If the gcc does not provide the splitstack feature the user gets linker
>>> errors - so he is responsible for that failure.
>>>
>> Or use
>>
>> feature.feature splitstack : on : optional ;
>> [ configure.check-target-builds
>> has_splitstack :<splitstack>on ]
>>
>> Where has_splitstack builds iff splitstack is available.
>>
> Looks better - but I need an additional BOOST_HAS_SPLITSTACK for enabling splitstack_allocator in the header file.
> How can I add a <define>BOOST_HAS_SPLITSTACK in the code above?

It should work to take the above code, replace feature.feature call with:

        feature.feature splitstack : on : optional composite :

and add:

        feature.compose <splitstack>on : <define>BOOST_HAS_SPLITSTACK ;

HTH,
Volodya