RE: [Boost-users] Re: install? and simple thread program.
On Fri, 5 Mar 2004, Michael Glassford wrote:
"Duong, Sanh N." <SANH.N.DUONG@saic.com> wrote in message
news:6A47CB4A48D1EA49A6F7AB618490D649069D8C3C@mcl-its-exs03.mail.saic.com...
All,
Does anyone have an example of how to install boost and bjam?
See the recently much improved Getting Started guide: http://boost.org/more/getting_started.html.
After you follow those instructions, boost will still not work.
Even if you were right, I think you're painting with too broad a brush here. But I think you're wrong.
You'll need to create links to all of the mangled library names. For example, in my case all of the libraries have either "gcc" or "gcc_1_31" mangled in. However, the examples (or more specifically the boost.python example) assume that the libraries have unmangled names.
The Boost.Python example should still work just fine, if you follow the instructions. bjam doesn't use the mangled library names when building with cross-project dependencies. It worked for me just now. I went into libs/python/example and did
bjam test
and everything passed. No funky linking should is needed.
When running bjam test, in libs/python/example I'd get a lot of errors about templates and vars not define. Another thing I noticed, when installing boost with bjam "-sGXX=g++" "-sTOOLS=gcc" "--prefix=/home/boost_1_31_0" install it would say, "Skipping Boost.Python library build due to missing or incorrect configuration couldn't find Python.h in "/include/python" When I point the PYTHON_ROOT and PYTHON_VERSION to the correct path, I'd get a lot of errors when compiling. Is there a step I'm missing here? Sanh.
"Duong, Sanh N." <SANH.N.DUONG@saic.com> writes:
On Fri, 5 Mar 2004, Michael Glassford wrote:
"Duong, Sanh N." <SANH.N.DUONG@saic.com> wrote in message
The Boost.Python example should still work just fine, if you follow the instructions. bjam doesn't use the mangled library names when building with cross-project dependencies. It worked for me just now. I went into libs/python/example and did
bjam test
and everything passed. No funky linking should is needed.
When running bjam test, in libs/python/example I'd get a lot of errors about templates and vars not define.
Let's see a few of them.
Another thing I noticed, when installing boost with
bjam "-sGXX=g++" "-sTOOLS=gcc" "--prefix=/home/boost_1_31_0" install
it would say, "Skipping Boost.Python library build due to missing or incorrect configuration couldn't find Python.h in "/include/python"
Right.
When I point the PYTHON_ROOT and PYTHON_VERSION to the correct path, I'd get a lot of errors when compiling. Is there a step I'm missing here?
Hard to say without seeing the errors. My guess is that you didn't set them correctly. Did you follow the directions at http://www.boost.org/libs/python/doc/building.html ?? -- Dave Abrahams Boost Consulting www.boost-consulting.com
"Duong, Sanh N." <SANH.N.DUONG@saic.com> writes:
When I point the PYTHON_ROOT and PYTHON_VERSION to the correct
"David Abrahams" <dave@boost-consulting.com> wrote in message news:ullmb6uhu.fsf@boost-consulting.com... path, I'd get
a lot of errors when compiling. Is there a step I'm missing here?
Hard to say without seeing the errors. My guess is that you didn't set them correctly. Did you follow the directions at
http://www.boost.org/libs/python/doc/building.html
??
One thing to check is that (for Win32 at least) if the PYTHON_ROOT and PYTHON_VERSION environment variable names are not defined in all upper case letters they won't be detected properly by the build process. This caused me problems at first. Mike
-- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (2)
-
David Abrahams -
Duong, Sanh N. -
Michael Glassford