Subject: Re: [boost] Request for a "Policy Review" regarding 'CMakeLists.txt'
From: Thijs (M.A.) van den Berg (thijs_at_[hidden])
Date: 2016-05-17 17:03:58
> On 17 May 2016, at 22:54, Peter Dimov <lists_at_[hidden]> wrote:
> Paul Fultz II wrote:
>> On Tuesday, May 17, 2016 at 1:19:24 PM UTC-5, Peter Dimov wrote:
>> > Paul Fultz II wrote:
>> > > Something like this:
>> > >
>> > > git clone git_at_[hidden]:boostorg/hana.git
>> > > mkdir build && cd build
>> > > cmake ../hana/
>> > > cmake --build .
>> > > cmake --build . --target check
>> > > cmake --build . --target install
>> > >
>> > > This builds, tests, and installs hana.
>> > I wonder how this workflow would look like if we assume Boost layout, > f.ex. from an extracted release tarball.
>> It should be the same., if boost supports cmake. So, boost should provide a top-level cmake that calls add_subdirectory for each library that has a CMakeLists.txt file. However, this can be done later.
> You're talking about building the whole Boost, and that's not what I meant. I asked about the equivalent of the above, building, testing and installing Hana, but from the directory structure of a Boost distribution.
Boost is a monolithic release, it might indeed be good to think about how the outcome of the CMake discussion interacts with the other profound change that has been worked on not so long ago: to model and reduce dependencies between libraries and break the monolithic structure.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk