How to build a boost dependent project using regular makefiles?

I'm working on a c++ project, and we recently needed to include a small part of boost in it. The boost part is really minimal (Boost::Python), thus, using bjam to build everything looks like an overkill (besides, everyone working on the project feels comfortable with make, and has no knowloedge of jam).

I made quite some tests already, but I cant find a way to include the formerly mentioned library in my makefile and make the build succesful.

All your help is deeply apreciated. :)


ANSWERS:


I had the same problem and found a solution in this tutorial. You 1) need to compile the source into an object file with the -fPIC gcc option, and 2) compile this object into a library with the -shared gcc option. Of course you have also to link against the Boost.Python library (generally -lboost_python, however for my debian system it is for example -lboost_python-mt-py25, I have also to add -I/usr/include/pythyon25). In my makefile I end up doing those two steps in one command. See also p. 13 of this presentation.


You can use Boost's bcp utility to extract only the subset of Boost you need. That will minimize your build time & size.

That doesn't answer your question, though. You may want to consider building the Boost.Python libraries separately and checking them directly into your source control system. Then nobody would need to build them.


If you're uncomfortable with bjam, you might want to consider using Boost.Cmake.
Alternatively you should at least be able to see more easily what they are doing then with the bjam files.


Run bjam from the makefile, just for building that part



 MORE:


 ? Boost.Python link errors under Windows/MSVC10
 ? Procedure for building and importing a Boost.python module using GCC?
 ? Boost.Python tries to link against python27.lib using Visual C++
 ? Unable to build Boost.Python
 ? Building Boost.Python
 ? Why does the Boost.Python example build fail?
 ? Building/including Boost.Python in VS2013
 ? project lib depends on package. How to expose interface
 ? How to change Visual Studio C++ initialization sequence for const string arrays in statically linked libraries
 ? How to change Visual Studio C++ initialization sequence for const string arrays in statically linked libraries