Re: [jamboost] [bbv2] Issues; is it ready for primetime?

From: Jürgen Hunold (hunold_at_[hidden])
Date: 2005-04-22 02:01:29

Hi Volodya !

On Thursday, 21. April 2005 12:41, Vladimir Prus wrote:
> On Thursday 21 April 2005 11:56, Vladimir Prus wrote:

> > > > Oh, I guess I forgot that "bjam --v2" should build something.
> > > > Does "bjam --v2 stage" work?

> > Ok, I'll fix this, meanwhile.
>
> Fixed. "bjam --v2" now really builds something, even without
> "install" or "stage". And "--with-foo" works too.

Unfortunately, all my libraries and apps link against python just 
because I configured it in order to get rid of the annyoing 
warnings ;-) But this is a minor thing, I can easily live with this 
behaviour...

Worse, the toolset contains a false library path, at least on Debian 
unstable. (full diff attached)

- libraries ?= $(root)/lib/python$(version)/config ;
+ libraries ?= $(root)/lib ;

My python .so files are in /usr/lib/ and corretly named libpython2.3.so

I can explicitly override this in the toolset initialisition, but the 
default library path just seems wrong.

Any comments ?

Yours,

Jürgen

-- 
* Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen, Eisenbahnbau
* voice: ++49 511 762-2529 ! und -betrieb, Universität Hannover  
* fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover
* hunold_at_[hidden] ! www.ive.uni-hannover.de
 --Boundary-00=_KFKaCNGBp3wIQ79 Content-Type: text/x-diff;
charset="utf-8";
name="python.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="python.diff"
Index: v2/tools/python.jam
=================================RCS file: /cvsroot/boost/boost/tools/build/v2/tools/python.jam,v
retrieving revision 1.3
diff -u -5 -p -r1.3 python.jam
--- v2/tools/python.jam	11 Apr 2005 11:07:07 -0000	1.3
+++ v2/tools/python.jam	22 Apr 2005 06:56:05 -0000
@@ -59,11 +59,11 @@ rule init ( version ? : root ? : include
rule init-unix ( version ? : root ? : includes ? : libraries ? )
{
root ?= /usr ;
includes ?= $(root)/include/python$(version) ;
- libraries ?= $(root)/lib/python$(version)/config ;
+ libraries ?= $(root)/lib ;
# Find the 'python' binary, which is used for testing.
# Look first in $(root)/bin, then in PATH.
local interpreter = [ common.get-invocation-command 
python : python : : $(root)/bin : path-last ] ;
 --Boundary-00=_KFKaCNGBp3wIQ79--