Denis Arnaud <denis.arnaud_bo...@m4x.org> writes: > 2009/11/4 troy d. straszheim <t...@resophonic.com> > > There is still a small issue, though, with a mpi.so library > > > That is not an error. This is the python extension for MPI. Python > extensions are loaded by python, they don't start with 'lib'. If you add > the directory containing mpi.so to your PYTHONPATH and execute > > >>> import mpi > > that file should be found and loaded. mpi.so will pull in > libboost_python.so and libboost_mpi.so, so you may need to add the lib dir > to your LD_LIBRARY_PATH as well. > > > As such, the (Python extension) mpi.so library cannot be included in any RPM > package, because it has no soname. Is there a CMake configuration option, so > that that mpi.so library gets a proper soname?
A few mails on this topic went by a while ago... nothing ever links "to" these python modules. They're loaded by the python interpreter; sonames don't really make sense. > Moreover, it could be a good idea to deliver it in a dedicated sub-directory, > for instance /usr/lib[64]/python2.6 or /usr/lib[64]/python2.6/boost, because > if > left in /usr/lib[64], there is no hint as to what that library is aimed at. > Do you know whether there is a CMake configuration option for that as well? AFAIK this is the only python module built by boost and nobody has given serious thought to where it should be installed. This is a large can of wriggly worms. /usr/lib[64]/python2.6/boost does sounds reasonable, the important thing is that it is on the system's PYTHONPATH. You'd also need to drop an empty __init__.py into that boost directory. -t _______________________________________________ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
