[pkg-boost-devel] Boost and Python 2.4

[Steve M. Robbins]

On Mon, Aug 13, 2007 at 02:03:55AM +0200, Domenico Andreoli wrote:
> On Sun, Aug 12, 2007 at 06:36:06PM -0500, Steve M. Robbins wrote:

> > I thought I might have a go at fixing this if I have some time
> > this evening.  I may not have the time, after all, but Dominik: if
> > this would interfere with any of your plans, do let me know.
> 
> before uploading 1.34.1 with python 2.4 only, I want to be sure there
> is no way in building two flavours of Boost.Python, 2.4 and 2.5.

It looks doable, but I've run out of time.  Here's what I've figured
out so far: the attached patch should build Boost.Python for 2.4 and
2.5.  The former is default, since it is currently default on Debian.


> it was required to change the soname, I would prefer to change the
> python 2.4 one, which is anyway going away probably before lenny.

I think there's nearly always 2 or more python versions officially
supported in Debian.  So it makes sense to decorate the Boost.Python
lib name and SONAME with the python version at all times, don't you
think?

-Steve
P.S.  I "corrected" the 
	$(bjam): CC=gcc-4.1
line in the diff without really understanding it.  What does
it mean to have a variable assignment as a dependency of a
target?  Shouldn't this be a straight variable assignment?
Does CC need to be assigned?


Index: debian/rules
===================================================================
--- debian/rules	(revision 14120)
+++ debian/rules	(working copy)
@@ -66,7 +66,8 @@
 ifeq ($(DEB_BUILD_ARCH), hppa)
 TOOLSET_CONFIG="using gcc : 4.2 : g++-4.2 : <define>_REENTRANT <compileflags>-mlong-calls ;"
 endif
-PYTHON_CONFIG="using python : 2.5 : /usr ;"
+PYTHON_CONFIG1="using python : 2.4 : python2.4 ;"
+PYTHON_CONFIG2="using python : 2.5 : python2.5 ;"
 
 exampledir = debian/libboost-doc/usr/share/doc/libboost-doc/examples
 htmldir = debian/libboost-doc/usr/share/doc/libboost-doc/HTML
@@ -75,7 +76,7 @@
 
 JAM = $(bjam) -d2 --user-config=$(shell pwd)/user-config.jam -sHAVE_ICU=1
 
-$(bjam): CC=gcc-4.1
+$(bjam): CC=gcc-4.2
 $(bjam):
 	cd tools/jam/src && sh build.sh cc && mv bin.*/bjam .
 
@@ -84,13 +85,15 @@
 	dh_testdir
 
 	echo $(TOOLSET_CONFIG) >> user-config.jam
-	echo $(PYTHON_CONFIG) >> user-config.jam
+	echo $(PYTHON_CONFIG1) >> user-config.jam
+	echo $(PYTHON_CONFIG2) >> user-config.jam
 
 	cd tools/bcp && $(JAM)
 	cd tools/inspect/build && $(JAM)
 	cd tools/wave/build && $(JAM)
 	cd tools/regression/build && $(JAM)
 
+	$(JAM) variant=release,debug threading=single,multi python python=2.5
 	$(JAM) variant=release,debug threading=single,multi
 	cd libs/python/pyste/install && python2.5 setup.py build
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-boost-devel/attachments/20070813/c339a1c6/attachment.pgp