From: David Abrahams (dave_at_[hidden])
Date: 2003-12-15 09:22:05
[posted to jamboost]
I've been having a problem with BBv1 wherein the fact that a feature
appears in a target's requirements doesn't force it to be included in
the BUILD, so bjam says there's a feature incompatibility and stops.
It appears to me that most of the Boost.Python Linux GCC-3.1 failures
are fixed by building with -sBUILD=<threading>multi. It also seems to
me that it shouldn't be neccessary to add that to the default-build
of every python target or to the global BUILD variable.
To see this for example, add <threading>multi to PYTHON_PROPERTIES or
the requirements of any of the python test targets.
I'm fairly certain it used to be that if the user didn't explicitly
specify a property and one of the targets in a dependency chain *did*
specify it as a requirement, it would always be added to the build
properties. Am I wrong? Can we do anything about this?
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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