Subject: [Boost-build] modular builds
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2015-05-04 10:58:27
after a long pause I'm looking again into boost.python. I would very
much like to be able to build boost.python not only as part of a full
boost build, but also in isolation, against prerequisites already
installed on my machine (I'm running Fedora, with boost libs installed
system-wide via yum...).
Ultimately it would be great to integrate any changes upstream so I
don't have to work on a fork. Users may then want to use a command-line
option to the `bjam` (or `b2`) invocation to indicate which versions of
prerequisites to build against. But for now, I'd be happy just to figure
out what changes I have to make to my Boost.Python tree (which I checked
out separately from github), to support a stand-alone build.
1) I have added a Jamroot file with a clone of the 'boost-install' rule
from Boost's own Jamroot file.
2) I have modified the 'tag' rule in the Jamfile.v2 so it doesn't call
Boost's 'tag' rule. As it requires the 'boostcpp' module, ...
3) ...I cloned the boostcpp.jam file from Boost.
When I now run `bjam` (in boost.python/build), I get the error from the
attached log. Any idea what may have gone wrong ?
Also, are the above steps 1-3 appropriate ? (I'd like to revisit the
entire process once I have got the stand-alone build working, as I
really don't want to
make changes to the boost.python repo that are incompatible with an
integrated build. But first things first...
-- ...ich hab' noch einen Koffer in Berlin...
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