Re: More Boost.Python questions

From: David Abrahams (dave_at_[hidden])
Date: 2004-11-19 17:30:01

Vladimir Prus <ghost_at_[hidden]> writes:

> Dave,
> V1 has this code for Python:
>
> # Normally on Linux, Python is built with GCC. A "poor QOI choice" in
> # the implementation of the intel tools prevents the use of
> # intel-linked shared libs by a GCC-built executable unless they have
> # been told to use the GCC runtime. This rule adds the requisite
> # flags to the compile and link lines.
> rule python-intel-use-gcc-stdlib ( toolset variant : non-defaults * )
> {
> ......
> }
>
> # Force statically-linked embedding applications to be multithreaded
> # on UNIX.
> rule python-static-multithread ( toolset variant : properties * )
>
> Do you recall, if those rules are needed for:
>
> 1. Any use of Python
> 2. Building of Boost.Python
> 3. Building of Python extension

I don't recall.

> It looks to me, for example, that python-intel-use-gcc-stdlib is only 
> important for building extensions, 

That seems right.

> and python-static-multithread is only 
> important for applications that link to Boost.Python.

I honestly don't know about that one.

> BTW, why python-static-multithread is needed? Unlike the first rule, there are 
> explanations.

Sorry, I don't know. You could take it out and watch the regression
tests break.

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