[pkg-boost-devel] Bug#452410: System Jamfiles not strictly needed

[Georg Schmid]

Hi Steve,

I was trying to build the Boost python tutorial (e.g.
/usr/share/doc/libboost1.35-doc/examples/libs/python/example/tutorial/) on my
Lenny machine as well. It is true, like you say, that if the system Jamfiles are
available, then the Jamroot given in the tutorial works.

What the Jamroot does however is include the build of boost itself and specify a
requirement on the (to be built) libboost_python. But on Debian, this library
has already been built and packaged. So I suggest to modify the Jamroot of the
tutorial so that it references the installed library instead of adding the
system Jamfiles (at least for this bug, adding them may still be useful).

The patch:

--- Jamroot     2009-05-21 22:01:18.000000000 +0200
+++ Jamroot.debian      2009-05-21 21:59:36.000000000 +0200
@@ -2,16 +2,17 @@
 # Software License, Version 1.0. (See accompanying
 # file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)

-# Specify the path to the Boost project.  If you move this project,
-# adjust this path to refer to the Boost root directory.
-use-project boost
-  : ../../../.. ;
+using python ;
+
+# Specify that the boost-python library exists under the name
+# boost_python. That is, because the library was installed at the
+# standard search path as /usr/lib/libboost_python.so, bjam will find
+# it automatically. No need to specify the absolute path.
+lib libboost_python : : <name>boost_python ;

 # Set up the project-wide requirements that everything uses the
-# boost_python library from the project whose global ID is
-# /boost/python.
-project
-  : requirements <library>/boost/python//boost_python ;
+# boost_python library.
+project : requirements <library>libboost_python ;

 # Declare the three extension modules.  You can specify multiple
 # source files after the colon separated by spaces.



Cheers, Georg