Re: [jamboost] RE: [C++-sig] version confusion

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-17 06:54:17

----- Original Message -----
From: "Achim Domma" <achim.domma_at_[hidden]>

> > A minimal Jamfile which does this sort of thing for v2 might be:
> >
> > subproject libs/python/test ;
> >
> > # bring in the rules for python
> > SEARCH on <module@>python.jam = $(BOOST_BUILD_PATH) ;
> > include <module@>python.jam ;
> > local PYTHON_PROPERTIES = $(BOOST_PYTHON_V2_PROPERTIES) ;
> >
> > extension my_ext : my_cpp1.cpp my_cpp2.cpp <dll>../bpl
> > : # any additional requirements, e.g. <define>MY_LIB
> > ;
>
> I just managed to build my first python extension with bpl and bjam, and
of
> course I have more questions now:
>
> - How can I tell bjam to link with third party libraries, which are not
> build with bjam ? The statement <dll>../bpl seems to rely on the bjam
folder
> structure.

You can use

<library-file>path/to/library.lib
OR
<library-path>path/to <find-library>library

in the requirements section of your bjam spec.

> - Is there an easy way to use bjam outside the boost source tree? As far
as
> I understand, bjam walks up the tree to find some jamfiles, but that
would
> fail if I invoke it outside the boost tree.

See http://www.boost.org/libs/python/doc/building.html, in particular the
link to http://www.boost.org/libs/python/example/project.zip

> greetings
> Achim
>
> PS.: I crossposted to c++-sig_at_[hidden] and jamboost_at_[hidden]
> because the original thread started in c++-sig, but is becoming more and
> more jamboost specific.

HTH,
Dave