Subject: Re: [boost] Boost CMake update
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2017-10-04 20:55:25
On 04.10.2017 16:49, Robert Ramey via Boost wrote:
> On 10/4/17 10:36 AM, Stefan Seefeld via Boost wrote:
>> On 04.10.2017 13:22, Rene Rivera via Boost wrote:
>>>> For one, I didn't mean to re-open a discussion about separating
>>>> cycles. I merely wanted to point out a limitation in the existing
>>>> Boost.Build logic, and how I hope that any future build system will
>>>> support stand-alone builds, so further modularization can at least be
>>>> considered and experimented with.
>>> Not entirely sure what you are referring to... But B2 doesn't have
>>> such a
>>> limitation. So perhaps I missed something something.
>> Perhaps b2 the tool doesn't have such a limitation, but b2 the boost
>> build infrastructure does, given that it's impossible to build library
>> Boost.X stand-alone, i.e. without starting from the superproject repo.
> Hmmm - I'm not seeing this.Â I always build all my tests from the
> serialization/test directory.Â This also automagically builds all the
> precursor libraries like boost/system etc.
That's my point: the current workflow lets b2 crawl outwards to find all
prerequisite library source trees to build. The use case I'm describing
would really only build the serialization library, with all
prerequisites being assumed to be already built and installed (somewhere).
-- ...ich hab' noch einen Koffer in Berlin...