Subject: Re: [boost] Request for a "Policy Review" regarding 'CMakeLists.txt'
From: Paul Fultz II (pfultz2_at_[hidden])
Date: 2016-05-17 19:50:39
On Tuesday, May 17, 2016 at 3:54:50 PM UTC-5, Peter Dimov 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
> > a top-level cmake that calls add_subdirectory for each library that has
> > CMakeLists.txt file. However, this can be done later.
> You're talking about building the whole Boost, and that's not what I
> I asked about the equivalent of the above, building, testing and
> Hana, but from the directory structure of a Boost distribution.
Ok, you could just do `cmake libs/hana` for the cmake step. However, this
won't build hana's dependencies. Another way would be for hana to provide a
target just for its test, so using `hana-check` instead of `check`:
git clone git_at_[hidden]:boostorg/boost.git
mkdir build && cd build
cmake --build . --target hana
cmake --build . --target hana-check
cmake --build . --target install
Another option would be to do something like bpm and place the libraries and
dependencies for hana in their own directory and then create a top-level
that calls `add_subdirectory` for each library, but I believe you were
referring to the tarball release, so this doesn't really apply.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk