Re: [jamboost] Re: Library files named with Python version

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2004-12-27 14:43:50

Rene Rivera wrote:
> Nicolas Fleury wrote:
> 
> 
>>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...
> 
> 
> I think the easiest would be to change 
> boost-root/libs/python/build/Jamfile to include the additional version 
> tag...

OK let me try this again as an attachment so that Yahoo groups doesn't 
eat part of the text..

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
 --------------090406030204040309010109 Content-Type: text/plain;
name="bpl-build.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="bpl-build.patch"
===================================================================
RCS file: /cvsroot/boost/boost/libs/python/build/Jamfile,v
retrieving revision 1.35
diff -u -r1.35 Jamfile
--- Jamfile	26 Jul 2004 15:33:26 -0000	1.35
+++ Jamfile	27 Dec 2004 19:36:42 -0000
@@ -63,6 +63,7 @@
$(bpl-linkflags)
<msvc-stlport><release>$(msvc-stlport-workarounds)
;
template extension
@@ -80,6 +81,7 @@
<define>BOOST_STATIC_LIB
$(bpl-linkflags)
<msvc-stlport><release>$(msvc-stlport-workarounds)
stage bin-stage : <dll>boost_python <lib>boost_python
 --------------090406030204040309010109--