From: Bruce S. <Bru...@nc...> - 2010-12-27 22:12:34
|
I got a little farther. Although the documentation looks like --library-path and -L should be synonyms, it seems like they aren't. With -L I do find the libraries for Python 3. But then when I try to run Visual, "import cvisual" fails because there's a search for libboost_python in /usr/libs which finds a version for Python 2.6, even if I've copied the Python 3 libraries to /usr/libs. The fundamental problem is that I don't see how to use distinctive names for the Python 3 libraries, such as "libboost3_python" instead of "libboost_python". I also tried ld -static and produced a large static library. But "import cvisual" is apparently unable to deal with a static library on Ubuntu. Bruce Sherwood On Sun, Dec 26, 2010 at 10:17 PM, Bruce Sherwood <Bru...@nc...> wrote: > I'm trying to build Visual on Ubuntu (10.10) for Python 3.1, where the > standard Python is Python 2.6, and the Boost 1.42 libraries are > installed for this version of Python. > > I've built the Boost 1.43 libraries for Python 3.1 and placed in my > own space the Boost folder of include files and, in a folder beside > the include files, the boost_python, boost_signals, and boost_thread > libraries. I altered the make file to specify linking these libraries > from my own directory rather than from the standard locations, as > follows: > > ld ..... --library-path=mylibs -lboost_python -lboost_signals > -lboost_thread .... > > What happens when I build looks like I'm linking against the > Ubuntu-installed libraries for Python 2.6, because when I try to run > Visual, I get an import error referring to > /usr/lib/libboost_python-py2.6.so.1.42.0, which is of course missing a > needed symbol. > > Can anyone shed any light on this? Thanks. > > Bruce Sherwood > |