Boost logo

Boost :

Subject: Re: [boost] Some statistics about the C++ 11/14 mandatory Boost libraries
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2015-05-13 14:10:49

On 13 May 2015 at 14:06, Stefan Seefeld wrote:

> >> Assuming a full breakup of boost libraries with well documented (and
> >> encoded) dependencies among them, I think a much more viable solution
> >> for everyone would be to let each boost library become its own project
> >> with its own release schedule etc.
> > Already there. APIBind makes it easier to iterate versions of a
> > library without breaking dependent libraries who can remain bound to
> > earlier versions. All in the same translation unit.
> Sounds useful. But "Already there" surely is somewhat of an
> overstatement. :-)

Already there in that the proposal already has that.

> For once, each of those stand-alone library projects needs a way to be
> built stand-alone, against already installed prerequisite libraries.

APIBind currently requires header only dependencies. That removes the
build system problem.

If Boost decides on a future build system solution, we can do better
than that.


ned Productions Limited Consulting

Boost list run by bdawes at, gregod at, cpdaniel at, john at