Re: [Boost-build] Two Problems with the Boost.Build...

From: David Abrahams (dave_at_[hidden])
Date: 2007-01-29 02:57:08

Jeffrey Holle <jeffreyholle_at_[hidden]> writes:

> Vladimir Prus wrote:
>> 
>> Using environment to configure python is not longer supported. Add
>> 	using python : 2.4 ;
>> to your user-config.
>
> Surprising.  Since directory info isn't transferred this way, I hope 
> python is stable on all systems that you support!

bjam --help python.init

  Rule 'python.init ( version ? : root ? : includes ? : libraries ? :
  cygwin-condition * )':

    Initializes the Python toolset. - version -- the version of Python to use.
    Should be in Major.Minor format, for example 2.3 - 'root' -- the install root
    for Python - 'includes' -- the include path to Python headers. If empty, will
    be guessed from 'root' - 'libraries' -- the path to Python libraries. If
    empty, will be guessed from 'root' - 'cygwin-condition' -- if specified,
    should be a set of properties which are present when we're building with
    cygwin gcc. This argument is not used yet.

    Example usage:

    using python 2.3 ; # Use default root using python 2.3 : /usr/local ; # Root
    specified, include and lib paths # will be guessed

    * version:
    * root:
    * includes:
    * libraries:
    * cygwin-condition:

The "init" rule is what implements 

  using python : 2.4 : path-to-root : path-to-includes :
    path-to-libraries ;

     

> A big help would be a commented "using python : 2.4 ;", or any other 
> version that is more current.  Shouldn't an internal library get the 
> same treatment that STLport and qt gets?

Python is not an internal library.  It's the thing provided by
www.python.org

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com