Re: [boost] Trying to build release, debug, profile variants into same stage directory

From: David Abrahams (dave_at_[hidden])
Date: 2007-05-02 06:40:08

on Tue May 01 2007, Vladimir Prus <ghost-AT-cs.msu.su> wrote:

> Richard Hadsell wrote:
>
>> Having discovered the profile variant (maybe it's new with 1.34.0), I
>> tried to build all 3 variants that I want and stage them to a common
>> directory.  Unfortunately, the profile variant doesn't add its own
>> suffix to the output library, the way the debug version does.  The
>> profiling library has the same name as the optimized (release) version.
> ........
>> diff -u -r1.1.1.1 common.jam
>> --- tools/build/v2/tools/common.jam     27 Apr 2007 17:12:56 -0000     
>> 1.1.1.1
>> +++ tools/build/v2/tools/common.jam     1 May 2007 17:04:37 -0000
>> @@ -792,7 +792,8 @@
>>        
>>      if <python-debugging>on in $(properties) { tag += y ; }
>>      if <variant>debug in $(properties) { tag += d ; }
>> -    if <stdlib>stlport in $(properties) { tag += p ; }
>> +    if <variant>profile in $(properties) { tag += p ; }
>> +    if <stdlib>stlport in $(properties) { tag += sp ; }
>>      if <stdlib-stlport:iostream>hostios in $(properties) { tag += n ; }
>
> Does anybody object to this change, for HEAD? I personally don't use neither
> stlport, nor (skewed for C++ code) gcc profiling, so I don't have an opinion
> either way.

I do, in it's current form.  I don't think stlport should have a
2-character tag.  Please pick one character.

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com
Don't Miss BoostCon 2007! ==> http://www.boostcon.com