Boost logo

Boost-Build :

Subject: Re: [Boost-build] rule execution order
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2016-10-16 19:27:22

On 16.10.2016 18:36, Rene Rivera wrote:
> On Sun, Oct 16, 2016 at 5:07 PM, Steven Watanabe <watanabesj_at_[hidden]
> <mailto:watanabesj_at_[hidden]>> wrote:
> On 10/16/2016 02:55 PM, Stefan Seefeld wrote:
> Is there any reason you can't just
> call sphynx-build directly from the Jamfile
> without going through make?
> Because that doc building should only run for the "boostrelease" target.

Can you elaborate ? I don't understand how the target that invokes the
doc build relates to how the doc build is implemented.
For simplicity's sake, right now I'd like a simple invocation of
`.../b2` in the 'doc/' directory to build all of Boost.Python's

A related question I was wondering about: is the documentation building
being CI-tested somehow & somewhere ? Can the generated docs be
inspected for manual / visual testing ?

I can see the auto-generated Boost.Python docs in, but that process uses SCons, not
Boost.Build, so I have no way to verify that what I'm working on right
now actually works (beside running it locally on my laptop, that is).


      ...ich hab' noch einen Koffer in Berlin...

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at