> Now it works. Well, yes, there were 3 issues. First, I had skipped the "make > install" part in "getting started with boost", i.e. I didn't have any > libboost* files (of which I know explicitly). Second, LD_LIBRARY_PATH was not > set and, third, libboost_python-gcc41-1_37.so.1.37.0 didn't exist after > making. I just copied "libboost_python-gcc41-mt-1_37.so.1.37.0" to > "libboost_python-gcc41-1_37.so.1.37.0" in $LD_LIBRARY_PATH/. > > Thank you very much for your quick response.
You're welcome. I remember that you mentioned bjam, and if you like it then continue with it, but don't trust the documentation website: many other tools can compile and link with boost.python, not only bjam. I'm using SCons but make and cmake works as well. I'm telling that because I really dislike bjam syntax and when I began with boost.python I thought that boost.python was not for me just because of this building tool. Also if you begin with boost.python you must have a look at pyplusplus (or Py++), it's a very convenient tool that parses your C++ headers and generates boost.python code almost automatically. I'm using it for two years now and I'm really happy with it. There is also one problem with boost.python in general: library tends to become bigger and bigger with the number of functions and classes that you interface. Compile-time may also become an issue at some point. My library (~7000 lines of C++, 15 classes) now takes 50sec on a 8 cores 3Ghz computer. About 45sec are for the boost.python bindings... I'm now considering switching to pybindgen, but it's still a very new project that lacks some features of boost.python. Just curious, for what type of project do you wish to learn boost.python ? Best, Adrien _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
