Boost logo

Boost-Build :

From: Nicolas Fleury (nidoizo_at_[hidden])
Date: 2004-12-15 16:01:59

Vladimir Prus wrote:
> On Tuesday 14 December 2004 20:14, David Abrahams wrote:
>>Nicolas Fleury wrote:
>>> I don't know if it has already been suggested, but may I suggest that
>>>Boost.Python built libraries be named with Python version, allowing
>>>libraries for multiple Python versions to coexist in the same Boost
>>>build hierarchy. For example:
>>>boost_python-vc7-mt-1_32.lib => boost_python-vc7-mt-1_32-py2_3.lib
>>I won't make that change for BBv1, since we're trying to retire it. But
>>for BBv2, it's right in line with the idea that the Python version
>>should be a feature. Volodya and I discussed that idea some weeks ago
>>and I described a way to handle it, but I don't know if he ever
>>implemented it.
>>Hmm, from looking at python.jam I don't think he did. In fact, I think
>>that file is really in a partially-complete state. Volodya?
> Right, it's in the works. I think it works for Linux, but not for Windows and
> using different python versions is not yet supported.

I have already built 1.32 with Python 2.3. If I want to hardcode a
workaround to rebuild 1.32 with Python 2.4 and producing another library
with a *_py2.4.lib and *_py2.4.dll (with automatic lookup of
*_py2.4.dll, not the *.dll that would still use Python 2.3), is it
something simple to do? What need to be changed? Don't care about ugly
solutions, it will only be built once. At worst I was thinking about
changing every "boost_python" by "boost_python-py2.4" in jamfiles...

Thx and regards,


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at