Boost logo

Boost-Build :

From: Toon Knapen (toon.knapen_at_[hidden])
Date: 2004-12-10 05:00:46


Vladimir Prus wrote:

>
> I was thinking about this recently and almost decided that the approach Toon
> has outlines is the right one. However, you're right that it's better to
> have a standard name of an option.
>
> The problem is this this:
>
> Jamroot:
>
> lib my_lib : my_lib.cpp ..//some_other_project ;
>
> If you run
>
> bjam --build_dir=/tmp/foo
>

We can make this as complex as we want. OTOH we can make it very simple
too. For instance we (with our projects) use 1 env.var. to define where
all 'derived objects' should go (e.g. ALL_LOCATE_TARGET). Every project
specifies it's build-dir (in the project-rule) to be
$(ALL_LOCATE_TARGET)/my-project-name.

So it's also up to the boost-build project to be
read-only-medium-friendly in this case.

 


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