From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-05-18 02:12:59
On Wednesday 17 May 2006 19:45, Michael Krasnyk wrote:
> I have Jamroot file to make a python extension:
> using python ;
> import python ;
> python-extension hello
> : hello.cpp
> : <include>/usr/local/include/boost-1_33_1
note that the above requirements are only needed if you're linking against
installed Boost.Python. If you have Boost source, the easiest way would be:
: hello.cpp path_to_boost_src/libs/python/build//boost_python
For a start, you can go to boost_src/libs/python/example, edit boost-build.jam
so that it refers to V2, and run "bjam --v2 getting_started1". On my Linux
box, this works fine.
> The first problem is how to specify automatically
> suffixes gcc, mt in the line
> <find-shared-library>boost_python-gcc-mt or
> make in other way linking with boost_python library?
For installed Boost.Python, you'd need to specify the name under which
Boost.Python is installed, I think.
> The second problem is that bjam produces libhello.so.
> How it's possible to make it as hello.so?
With CVS version of Boost.Build, there's no "lib" prefix. You can download the
current nighly build from http://boost.org/boost-build2
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk