Re: Python initialization in V2

From: David Abrahams (dave_at_[hidden])
Date: 2005-02-11 11:19:31

Vladimir Prus <ghost_at_[hidden]> writes:

> I'm still nibbling at Python support in V2. This time the question is how to 
> find Boost.Python library.
>
> Say, user writes:
>
> using python : 2.3 ;
> python-extension getting_started : getting_started.cpp ;
>
> The 'python-extension' rule must arrange for Boost.Python 
> to be linked with the created python extension. 

Well the Boost.Python library isn't required for all Python
extensions; just the ones built with, er, Boost.Python ;-)

> I see two approaches
> to find Boost.Python
>
> - Just grep relatively to BOOST_BUILD_PATH, like boostbook does

> - Allows the user specify explicit location.
>
> I think it's best to allow both approaches:
>
> # Tries to find Boost.Python form BOOST_BUILD_PATH
> using python : 2.3 ;
>
> # Explicit 'using bpl' specifies the location of Boost.Python
> using python : 2.3 ;
> using bpl : /home/ghost/Work/boost/libs/python ; 
>
> Comments?

I'm highly confused. Why isn't bpl just like any other library?

You just use the standard ways of referring to either prebuilt or
project-based libraries. No?

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