Boost logo

Boost-Build :

From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-06-18 10:24:37


[2003-06-18] Vladimir Prus wrote:
>> --- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
>> I've got couple of questions, not really related to this milestone
>> though.
>>
>> 1. In hello example we've got an example of nifty symlink rule. It
>> works well, however if you do 'bjam release' both debug and relase
>> version would be compiled.
>> Attempt to do 'bjam hello_release' fails with
>
>Right. To achive the desired effect you should say....
>
> bjam symlink#1
>
>.... which means there's no reasonable way to achieve it. So, the problem
is
>that
>
> symlink hello_release : hello/<variant>release ;
>
>creates main target "hello_release" from the user point of view, but
>Boost.Build does something different. I think we should fix this. Rene,
>symlink was implemented by you, what do you think.
>
>(Also note that new target-id allows
> symlink links/hello_release : hello/<variant>release ;
>
>to declare main target "linkgs/hello_release", which will even be usable
>)

Sure fixing it would be nice ;-) Problem is which name of the target do we
use in this situation:

symlink hello_release hello_debug : hello/<variant>release
hello/<variant>debug ;

As what's internally generated are three targets:

symlink-targets; symlink#?
file-target; hello_release
file-target; hello_debug

-- grafik - Don't Assume Anything
-- rrivera (at) acm.org - grafik (at) redshift-software.com
-- 102708583 (at) icq

 


Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk