Subject: Re: [Boost-build] Running `make` from BB
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2016-10-14 11:04:46
On 14.10.2016 10:57, Rene Rivera wrote:
> On Fri, Oct 14, 2016 at 9:42 AM, Stefan Seefeld <stefan_at_[hidden]
> <mailto:stefan_at_[hidden]>> wrote:
> On 14.10.2016 10:28, Rene Rivera wrote:
> > Is this documentation that will be integrated into the general Boost
> > release build? I ask because there are special requirements for
> > In an ideal world I, personally, wouldn't need to do anything. But
> > since the release building rebuilds all the documentation I need to
> > know what tools need to be installed to build it.
> Yes, this will build the NumPy part of the Boost.Python doc.
> "Integration" simply means that the toplevel index contains a relative
> URL to the NumPy doc. The development environment needs to have sphinx
> (python-sphinx in a typical Linux distro) installed.
> Yeah.. It's not that simple :-) The release scripts are capable of
> running on three different CI providers (two Linux and one Windows),
> and can run locally in CLI (which is how I test them on MacOS).
> Although the release build tasks currently do not run on Windows (so
> it's relatively safe to ignore that OS in this case). But generally
> all the tools involved need to run on various operating systems. Which
> means figuring out what commands I need to invoke to install whatever
> is needed.
Yes, I understand. This is why a typical sphinx-based documentation
provides both a Makefile as well as a 'make.bat' file, so calling `make`
will work on UNIX-like systems (Linux, OSX) where the "make" tools is
available, as well as Windows, where this will translate into an
invocation of the "make.bat" script.
> For reference here's the two scripts involved in building the release:
-- ...ich hab' noch einen Koffer in Berlin...
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