Subject: Re: [boost] Request for a "Policy Review" regarding 'CMakeLists.txt'
From: Paul Fultz II (pfultz2_at_[hidden])
Date: 2016-05-18 00:01:05
> On May 17, 2016, at 8:09 PM, Peter Dimov <lists_at_[hidden]> wrote:
>
> Can we, and what is the best way to, achieve functionality such that 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
>
> works for the people who want a standalone Hana, and yet this
>
>> > > git clone git_at_[hidden]:boostorg/boost.git > > mkdir build && cd build > > cmake ../boost > > cmake --build . --target hana > > cmake --build . --target hana-check > > cmake --build . --target install
>
> also works? (And in that latter case,
>
> cmake --build . cmake --build . --target check
>
> to work as well, building and testing everything.)
Yes it can, but requires some coordination when searching for internal dependencies. Standalone builds would find dependencies using `find_package`, but in the superproject build, the search for internal dependencies would be a no-op, since the targets already exist, elsewhere.
>
> _______________________________________________
> Unsubscribe & other changes: http://listarchives.boost.org/mailman/listinfo.cgi/boost