From: Andrey Melnikov (melnikov_at_[hidden])
Date: 2005-07-07 14:50:45
Vladimir Prus wrote:
> 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 ;
I don't want this any more. I thought I would have to add build-dir to
every subproject like I did in VS.
>>>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
Do we have both install and stage rules?
project my : build-dir "../intermediate" ;
hello.cpp "null/null.cpp" :
and it worked too. Is such usage deprecated now?
> 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
>>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
> This won't handle differences in other build properties, though.
Well, handling all differences isn't necessary. Moreover, in production
environment it's a bad idea to have build properties not described in
named configurations. So in fact configuration name will be enough for me.
Now I'm far away from that point though. I can't write jamfiles even for
rather simple projects yet.
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