|
Boost-Build : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-07-06 10:15:37
Hi Andrey
> Can I use something like
>
> project yours : build-dir ($Jamroot)"../build" ;
Why would you want this? "../build" is taken relatively to file where it's
used (Jamroot) already. If you really want this, you can do:
path-constant HERE : . ;
project yours : build-dir $(HERE)/../build ;
> > Separating .obj and .exe targets is harder. Basically, I never though
> > about it, so have no idea what it will take. I need this to move around
> > in my head for a while, or if you have any suggestions -- I'm all ears.
>
> "Stage" directory will be enough. Is bbv2 staging described somewhere in
> the docs?
Maybe
http://boost.org/boost-build2/doc/html/bbv2/advanced/builtins/targets.html#bbv2.builtins.stage
If that's not enough, Boost's top-level Jamfile can serve as example.
> For debugging, multiple components of a project have to be put
> ("staged") into the same folder. Single stage folder for all project
> configurations is a bad idea because different configurations go to the
> same dir.
>
> What is the best way to put consistently configured outputs from
> subprojects to the same dir? How can I implement "solution
> configuration" MSVC feature which allows me to specify consistency rules?
install dist : whatever : <variant>debug:<location>debug
<variant>release:<location>release
;
This won't handle differences in other build properties, though.
- Volodya
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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