Re: [boost] Request for a "Policy Review" regarding 'CMakeLists.txt'

On May 17, 2016, at 8:09 PM, Peter Dimov wrote:

Can we, and what is the best way to, achieve functionality such that this:

...

...

...

...

git clone git@github.com: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@github.com: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://lists.boost.org/mailman/listinfo.cgi/boost