Re: Boost.Python V1 questions

From: David Abrahams (dave_at_[hidden])
Date: 2004-11-13 18:28:43

Vladimir Prus <ghost_at_[hidden]> writes:

> On Saturday 13 November 2004 05:26, David Abrahams wrote:
>
>> > # Tries to find the Python root
>> > using python ;
>> > # Specifies everything manually
>> > using python : /usr/include/python2.2 ........... ;
>>
>> Looks good to me.
>>
>> > Another approach is to allow several Python versions:
>> >
>> > using python : 2.2 : .......... ;
>> >
>> > is this needed, in your opinion?
>>
>> It's needed for people like me who want to be able to test against
>> multiple Python versions.
>
> Ok. Is "python-version" property OK with you? So that it's possible to write:
>
> bjam python-version=2.2 python-version=2.3
>
> ?

Well, shouldn't this be a sub-property so you can write

bjam python-2.2 python-2.3

just like you can write

bjam vc-7.1 vc-6.5

??

>>
>> I'm not sure what you mean. bjam invokes cygwin gcc. Do you mean
>> that bjam must be invoked under the cygwin shell? That's not true;
>> you can build and test for cygwin gcc under an NT shell. I did that
>> in part so I could test for cygwin and windows with a single bjam
>> invocation.
>
> So when running bjam in NT, you'll specify "/usr" for CYGWIN_PYTHON_ROOT and 
> that will eventually be passed to cygwin gcc -- which can understand the 
> "/usr" syntax. And NT bjam never does anything with "/usr" which requires 
> filesystem access? 

I don't know what you mean here.

> I was confused by the fast that NT bjam can use cygwin paths.

Or here.

> So, when manually initializing python we need either to pass two paths:
>
> using python : 2.3 : c:/python /usr/python ;
>
> or allow to specify specific properties in initialization:
>
> using python : 2.3 : c:/python ;
> using python : 2.3 : c:/python : <toolset>gcc <toolset-flavour>cygwin ;

using python : 2.3 : /usr/python : <toolset>gcc <toolset-flavour>cygwin ;

Something like that. I favor the latter. The former is too implicit.

>> You'd have to ask the Python developers why.
>
> If that's the way Python works, I'll just live with that.

That's basically what I decided to do as well ;-)

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com