Subject: Re: [Boost-build] build system changes for stand-alone build of Boost.Python
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2015-05-29 14:34:40
On 5/26/2015 10:59 PM, Stefan Seefeld wrote:
> as mentioned previously, I would like to decouple Boost.Python from the
> rest of Boost as far as building and releasing is concerned.
> I have forked the official Boost.Python repo and am working on my own
> "standalone" branch
> (https://github.com/stefanseefeld/boost.python/tree/standalone). Once
> things work correctly, I plan to push them upstream.
> I would very much appreciate if someone from the Boost.Build team could
> review these changes:
> The biggest chunk of this change is the addition of the "boost.jam"
> file, which I hope I can remove again soon, once it made its way into a
> Boost.Build release. (I'm working right now with Boost.Build 2014.10,
> which doesn't have it.)
I've made a couple of comments there.
> The rest should be pretty self-explanatory. (Note that despite my
> original plans to support both, standalone as well as integrated builds,
> I now think that standalone-only builds should suffice, as there is no
> point in keeping Boost.Python inside Boost (as far as builds and
> releases are concerned) once standalone builds fully work.)
It appears that forcing users to obtain Boost.Python separately just
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