Re: [boost] [Git] Documentation for Git and Modular Boost conversion

Subject: Re: [boost] [Git] Documentation for Git and Modular Boost conversion
From: Beman Dawes (bdawes_at_[hidden])
Date: 2012-12-16 08:12:50

On Sat, Dec 15, 2012 at 9:10 PM, Dave Abrahams <dave_at_[hidden]> wrote:
>
> on Sat Dec 08 2012, Andrey Semashev <andrey.semashev-AT-gmail.com> wrote:
>

>> Maybe I missed it somewhere but do I understand correctly that develop
>> branch corresponds to the current trunk? Also, what branches will be
>> tested?
>>
>> I would also like to see instructions of checking out and composing a
>> monolithic Boost distribution, possibly with (or without) only
>> selected libraries.
>
> Short answer:
>
>   git clone --recursive https://github.com/boost-lib/boost.git
>
> gets everything.  If you start with a non-recursive clone then you can
> control which submodules you get; see the Git documentation (yes, a
> more complete answer should go on the wiki).
>
>> As I understand, the common boost/ directory with links to library
>> headers would have to be recreated somehow.
>
>   cd boost
>   cmake -P forward_headers.cmake

At the time Andrey asked the question, that hadn't been documented
yet. It is now covered by:

https://svn.boost.org/trac/boost/wiki/TryModBoost

>
>> And is there a way to specify dependencies between libraries?
>
> Some of that is already present in the Jamfiles.
>
>> Is it possible to checkout lib A and everything it requires?

Added to https://svn.boost.org/trac/boost/wiki/ModCvtFAQ

--Beman