Subject: Re: [boost] Announcement: Faber, a new build system based on bjam
From: Julian Faber (boost_at_[hidden])
Date: 2017-11-20 22:23:32
not overly happy about the name - I think v20.0 or so of Faber, now into
its sixth century of existence, is just about good enough! But obviously
I don't have sole claim to the name
Long time list lurker, Jools (Faber)
On 10/11/2017 14:40, Stefan Seefeld via Boost wrote:
> about a year ago I started to experiment with a new Python frontend for
> Boost.Build. After many iterations of prototyping things are starting to
> fall into place, and the project stabilizes.
> I'm thus happy to announce the release of Faber version 0.2:
> code: https://github.com/stefanseefeld/faber
> docs: https://stefanseefeld.github.io/faber
> While Faber retains most of the features from Boost.Build, it is
> redesigned from the ground up. bjam is still used as scheduling engine,
> but everything else is written in Python. In particular, Jamfiles are
> replaced by fabscripts, which are essentially Python scripts. The
> project contains a range of examples to demonstrate various simple
> use-cases, from a simple "hello world" example to demos involving
> autoconf-style config checks, and unit testing.
> I have added build logic to Boost.Python to use Faber on Travis-CI as
> well as AppVeyor, which also is a good litmus test for Faber's capabilities.
> I'd be very interested in feedback as well as contributions. Perhaps it
> might become possible one day to integrate Faber with other efforts to
> add a Python frontend to Boost.Build.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk