Subject: Re: [boost] Cmake
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2017-06-24 16:07:37
On 24.06.2017 12:03, Rene Rivera via Boost wrote:
> On Sat, Jun 24, 2017 at 10:57 AM, Stefan Seefeld via Boost <
> boost_at_[hidden]> wrote:
>> On 24.06.2017 04:59, Peter Dimov via Boost wrote:
>>> There is considerable interest in Boost supporting CMake, but it seems
>>> that everyone has different ideas as to what this support will entail.
>>> After deliberation and discussions, I have identified the following
>>> (separate) scenarios:
>> I'm a bit confused by the listing, as you use the term "user" in quite
>> different ways.
>>> 1. The user installs a Boost release as usual with `b2 install`, which
>>> makes the installation visible to CMake and usable via
>>> 2. The user brings several Boost libraries as git submodules into his
>>> CMake-based project and uses add_subdirectory in his CMakeLists.txt to
>>> link to them.
>>> 3. The user uses CMake to install an individual Boost library, which
>>> is then available for find_package.
>>> 4. The user uses CTest to run the tests of an individual Boost library.
>>> 5. CMake is supported as a way to build and install the entire Boost,
>>> in place of b2.
>>> 6. CTest is supported as a way to run the tests for the entire Boost,
>>> in place of b2.
>> All but 1) are addressed at boost developers, i.e. people who want to
>> build (, test, etc.) boost itself. Only 1) is concerned about users who
>> want to use boost as external dependency to their own project.
> I've been a "user" of Boost doing #2 in some of my projects. And I wrote b2
> support to enable that use case (non-instrusively and external -- unlike
> this concept -- so far)
So what's the reason you prefer (at least in that context) building
boost as an integral part of another project, rather than referring to
it as an external (pre-installed) dependency ?
-- ...ich hab' noch einen Koffer in Berlin...
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk