Re: [boost] [CMake] Status of cmake support.

Subject: Re: [boost] [CMake] Status of cmake support.
From: mike.dev_at_[hidden]
Date: 2018-02-23 23:48:01

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Stefan
> Seefeld via Boost
> Sent: Wednesday, February 21, 2018 1:38 AM
> 
> On 20.02.2018 19:26, Louis Dionne via Boost wrote:
> > if library authors don't
> > want to spend time adding CMake support themselves, it should be
> > possible to just copy the files in [2] for their library. Paul, you
> > can correct me if anything here is incorrect.
> >
> > [1]: https://github.com/boost-cmake/bcm
> > [2]: https://github.com/boost-cmake/boost
> 
> At the risk of repeating myself: you present too simplistic a picture.
> It sounds as if library authors either are willing to do the transition
> themselves, or are happy to accept someone else writing some files that
> they can then "just copy". The OP however asked about "support", which is
> far more than adding some CMake files to their respective repos. It includes
> helping users who run into (build) issues compiling their library. And I still
> don't see where that support is going to come from.
> 

Actually, I'd personally be quite happy with just some basic cmake files, as long as there is a common structure behind them, they are properly integrated with the main project and they make boost libraries accessible via find_package. Thing is: With cmake, I can usually fix most problems myself because I use it everyday in other projects. With boost build I can't (not that I had any problems so far). But admittedly, once cmake becomes the official build system for boost, some level of support probably has to be provided (whatever support means in that context).