Boost logo

Boost-Build :

From: Pedro Ferreira (pedro.ferreira_at_[hidden])
Date: 2005-06-02 10:23:04

Hi Volodya,

----- Original Message -----
From: "Vladimir Prus" <ghost_at_[hidden]>
To: <jamboost_at_[hidden]>
Sent: Thursday, June 02, 2005 9:24 AM
Subject: Re: [jamboost] rename library when stage-ing broken ?

> On Tuesday 31 May 2005 18:31, Pedro Ferreira wrote:
>> >> Have I missed an update on
>> >> ?
>> >
>> > No, the <name> feature is still not there. Does "_d" stands for
>> > "debug"?
>> > Then,
>> > maybe using the full-blown <tag> feature would be a better approach?
>> I'd say both are useful: <name> for the simplest cases, <tag> when more
>> control is needed.
> I now remember yet another problem with <name>. If we allow to use it
> everywhere where <tag> is OK, then what does the following means:
> lib a : b : <name>liba ;
> Is this a prebuilt library that simply depends on 'b'? Or is it regular
> library, which a different name?
> You see, <name> unfortunately and inadvertently became overloaded, and I
> don't
> know which of the overloaded meanings is easier to kill.

Agreed, but I just wanted it to be available for install, not for all other

What I meant to do was something like:

feature.feature build-type : commercial evaluation ;
install License : License_Commercial.txt : <location>doc <name>License.txt
<build-type>commercial ;

install License : License_Evaluation.txt : <location>doc <name>License.txt
<build-type>evaluation ;

This would select the appropriate file and install it with the same name. Of
course, I could do it differently but I think it would be an useful feature.



Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at