Boost logo

Boost-Build :

From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2007-07-21 11:30:57

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.

You possibly mean bjam.

When starting in RC_1_34_0 I tried to put
into the build-system.jam file just before
the call to the boost-build rule, i.e.:

BOOST_ROOT = $(.boost-build-file:D) ;
boost-build tools/build/v2 ;

then in /usr/share/boost-build/bootstrap.jam I added:

.bootstrap-file = $(.bootstrap-file:D)/kernel/bootstrap.jam ;
include $(.bootstrap-file) ;

Then in RC_1_34_0 I called:
bjam --debug-configuration which yielded:

notice: found boost-build.jam at
BOOST_BUILD_PATH is /usr/share/boost-build
notice: loading Boost.Build from /usr/share/boost-build
BOOST_BUILD_PATH is /usr/share/boost-build

The second debug output from ECHO is at least in contradiction to the
documentation which says:

The boost-build rule adds its (optional) argument to the front of
BOOST_BUILD_PATH, and attempts to load bootstrap.jam from those directories.

I would expect "front" beeing the same as "left" or "first".

So since the boost-build rule adds the path to the back the default path
gets higher precedence. I feel like this is the least one would expect, not?

Volodya, will it be hard to change the boost-build rule?


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at