Subject: [boost] [cmake] Pull request announcement
From: mike.dev_at_[hidden]
Date: 2018-09-15 08:11:33
> -----Original Message-----
> From: Boost <boost-bounces_at_[hidden]> On Behalf Of Edward
> Diener via Boost
> Sent: Friday, September 14, 2018 8:05 PM
> To: boost_at_[hidden]
> Cc: Edward Diener <eldiener_at_[hidden]>
> Subject: Re: [boost] [cmake] Pull request announcement
>
> On 9/14/2018 10:20 AM, Peter Dimov via Boost wrote:
> > Edward Diener wrote:
> >> On 9/14/2018 7:44 AM, Mike Dev via Boost wrote:
> >> > Dear all,
> >> >
> >> > unless I'm encountering an overwhelming resistance to this idea here
> >> on > the ml, I intend to create a batch of PRs that introduce minimal
> >> cmake > support to a large subset of boost libraries (maybe even all).
> >>
> >> The practical problem for most libraries, which are largely
> >> header-only, is converting the library jamfile for tests and building
> >> docs into CMake terms.
> >
> > That's not what the proposed minimal support is about (IIUC). The goal
> > here is for people to be able to use a local installation of Boost (as
> > cloned from Github, perhaps as a submodule) from their CMake projects
> by
> > including the top-level CMakeLists.txt and then linking to the
> > appropriate imported targets.
> >
> > Tests, docs, are not in scope. Neither is building multiple variants,
> > staging, or installation.
>
> In which case CMake support in Boost evidently means that Boost Build
> will continue as the means to do tests and build the docs. That is fine
> with me but must be understood by the Boost Steering Committee and
> Boost
> developers/maintainers as part of Boost using CMake.
>
I'm pretty sure the desire of the steering committee, many users and probably
A lot of boost maintainers is that b2 gets completely replaced by a cmake based
solution someday (e.g. in the form of BCM).
However, I as a user would be very happy to at least have a solution that covers
80% of my use cases and that can be implemented now (by me alone if necessary)
instead of further hoping that this full replacement comes "soon"