Subject: Re: [Boost-build] Output directories of Boost Build
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2015-09-19 11:49:51
Let me use an example with shorter paths, so that I can actually type on a
small screen. Say you have Boost source in /tmp/boost, then the
build-directory property in jamroot will cause build to go to
If you specify --build-dir=/tmp/build, that will change to
/tmp/build/boost/gcc/... - note that bin.v2 is completely overridden, and
'boost' is added, taken from project declaration in Jamroot. This allows
--build-dir to work if the build spans multiple Jamroot files.
Stage and install dirs are not handled by Boost.Build, but by Boost C++
libraries. If you run b2 --help in Boost C++ root, you will see two options
that control those directories.
On Sat, Sep 19, 2015, 17:45 Edward Diener <eldiener_at_[hidden]> wrote:
> On 9/19/2015 8:38 AM, Niklas Angare wrote:
> > "Edward Diener" <eldiener_at_[hidden]> wrote:
> >> Is there a general way to control the location of Boost Build output
> >> directories, or are they always relative to the source directory, or
> >> perhaps relative to the Boost top-level directory ?
> > I found this in Jamroot with a quick search for bin.v2 in the repository
> > project boost
> > ...
> > : build-dir bin.v2
> >> I would like to share my Boost git repository between different Window
> >> OSs in a multi-boot machine, using a common NTFS drive. But I want to
> >> have the output from Boost build go to different local drives for each
> >> OS.
> > With a further search I found the --build-dir command-line option to b2
> > that would seem to solve your problem.
> > http://www.boost.org/build/doc/html/bbv2/overview/invocation.html
> I am not sure what this means in the documentation.
> If currently my local Boost git repository from source is at
> C:/Programming/VersionControl/modular-boost do I specify the --build-dir
> as 'C:/Programming/VersionControl/modular-boost' to ensure that the
> output of tests goto C:/Programming/VersionControl/modular-boost/bin.v2
> ? What about install and stage directories ? Do they then go to
> sub-directories relative to C:/Programming/VersionControl/modular-boost
> if I set --build-dir as 'C:/Programming/VersionControl/modular-boost' ?
> Unsubscribe & other changes:
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