Subject: Re: [boost] [cmake] Pull request announcement - update
From: Gavin Lambert (boost_at_[hidden])
Date: 2019-01-07 06:08:05
On 5/01/2019 00:03, mike wrote:
> For that, the cmake file in libfoo has to
> - provide the target Boost::libfoo
> - attach the dependency information for Boost::libfoo
> - attach the proper include directory for Boost::libfoo
> - if necessary, build libfoo with whatever toolchain
> and compile flags the parent cmake project defines
> - if necessary, attach any necessary compile definitions
> to Boost::libfoo
Does this assume/require a direct git checkout of the individual modules
(separate include directory per library) or can it also work with a
release bundle (common include directory)?
> For a quick overview, I uploaded a picture of the boost
> dependency graph (code based on boostdep) that shows
> which libraries Have a cmake file in their root and
> which don't .
I note that there are some green nodes which have red dependencies.
Presumably this means that the library has some CMake support but it may
or may not support the suggested workflow?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk