From: David Abrahams (dave_at_[hidden])
Date: 2005-04-28 07:10:03
Vladimir Prus <ghost_at_[hidden]> writes:
> Ouch! The site-config file initializes stlport, which is a project itself, and
> so tries to inherit from 'user-config', that's not defined yet!
> I've modified the logic so that "standlone" project (those that don't
> correspond to Jamfiles), do not inherit from user-config.
> Can you try again?
I think one problem is that
# Support for Python and the the Boost.Python library.
# This module defines
# - a project 'python' with a target 'python' in it, that corresponds
# to the python library
Which "python library?" Boost.Python, or Python itself?
Can't I get support for Python without bringing in
# - a main target rule 'python-extension' which can be used
# to build a python extension.
# Extensions that use Boost.Python must explicitly link to it.
rule init ( version ? : root ? : includes ? : libraries ? : cygwin-condition ? )
rule python-extension ( name : sources * : requirements * : default-build * :
usage-requirements * )
So why aren't there any comments describing the arguments to init and
It appears that the includes argument to init is never even used.
What's up with that?
Ambiguity and lack of comments make this needlessly unhelpful.
-- 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