From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2007-07-21 12:14:14
Vladimir Prus wrote:
> Hmm, I think we probably should modify Boost to always use in-tree
> Boost.Build, to make sure it's always can be built.
Although I think a clear priorization scheme for the paths would be
nicer (see my other posts), I found an easier solution that has the same
effect (without the need to modify jam source):
In boost-build.jam of boost root prepend the call to boost-build rule with:
BOOST_BUILD_PATH = ;
This will wipe out any other paths and make the intent clear to use the
build system that is hosted in the current boost tree from where the
bjam command is being invoked.
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