Subject: Re: [Boost-build] building boost.python
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2015-05-08 12:22:39
On 05/08/2015 10:03 AM, Stefan Seefeld wrote:
> I'm trying to build the boost.python examples, without success.
> The build system looks suspicious, so I'd like to start by understanding
> what it is supposed to do, before I try to fix anything.
> https://github.com/boostorg/python/tree/master/example contains a
> boost-build.jam file with
> # Edit this path to point at the tools/build/v2 subdirectory of your
> # Boost installation. Absolute paths work, too.
> boost-build ../../../tools/build/v2 ;
> That path no longer exists on github (there is no "v2" directory). But
> even if I remove "/v2", it raises an error. What does this line do ?
I think it should be .../tools/build/src now.
The point of boost-build.jam is to allow
b2 to find the jam sources for Boost.Build.
It's no longer needed if you're using an
installed version of Boost.Build.
> Jamfile doesn't contain any explicit targets, so what logic defines what
> an invocation of `bjam` (or `b2` as the case may be) should do ?
I see several targets in libs/python/example/Jamroot.
python-extension and run-test both declare targets.
> Next I tried to build the boost.python documentation, which tries to exeute
> "python" -gdt --source-url=./building.rst --link-stylesheet
> --traceback --trim-footnote-reference-space
> --footnote-references=superscript --stylesheet=../../../rst.css
> building.rst bin/gcc-4.9.2/debug/building.html
> which raises the error "Unknown option: -g"
> Any idea what I may be missing ?
There are two spaces between "python" and -gdt. I'd
guess that's where the name of some python script
is supposed to be.
> (As you may guess, I'm trying to get up to speed with boost.python after
> a few years of lurking in the background. And while I think I have a
> good handle on the boost.python code itself, I'm still struggling with
> the build system. :-( )
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk