$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] [CMake] Status of cmake support.
From: P F (pfultz2_at_[hidden])
Date: 2018-02-21 02:42:18
> On Feb 20, 2018, at 6:26 PM, Louis Dionne via Boost <boost_at_[hidden]> wrote:
>
> On Tue, Feb 20, 2018 at 12:18 AM, Mike via Boost <boost_at_[hidden]>
> wrote:
>
>> Hi everyone,
>> since I couldn't find any official information about that, I wanted to
>> ask if there is any new information about the cmake support in boost
>> (since the initial discussion on the ml after the steering committee's
>> announcement)?
>
> Is there some agreement on how to do the transition or at least a
>> popular formal/informal proposal?
>>
>
> As far as I can tell, the current status is that we're waiting for a formal
> review of Paul Fultz's BCM library [1] to happen, which is currently
> blocked on getting a review manager. The goal of BCM is to provide a few
> CMake utilities to make it easier for Boost libraries to implement support
> for CMake in a consistent manner. If BCM is seen as the proper way to do
> CMake within Boost, I guess the logical next step would be to start using
> BCM to add CMake support in the libraries. Unless I'm mistaken, Paul has
> already basically done this for all libraries [2]; 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.
That is correct. I have built a collection cmake modules to aid in building cmake scripts. We are looking for a review manager for this, as the original manager will not be able to. In the mean time, I have done an initial implementation of cmake across boost, as a proof-of-concept. After the cmake modules are accepted in boost, the goal would be to integrate these initial cmake files across boost after authorâs modifications.
Thanks,
Paul