Subject: Re: [boost] [Git] Documentation for Git and Modular Boost conversion
From: Dave Abrahams (dave_at_[hidden])
Date: 2012-12-15 21:10:00
on Sat Dec 08 2012, Andrey Semashev <andrey.semashev-AT-gmail.com> wrote:
> On December 7, 2012 8:54:33 PM Beman Dawes <bdawes_at_[hidden]> wrote:
>> We are starting to pull together documentation for the Git and Modular
>> Boost conversion.
>> Comments and corrections welcome!
>> I'm particularly interested in unanswered questions you have after
>> reading these initial docs.
> Great work, thank you.
> Maybe I missed it somewhere but do I understand correctly that develop
> branch corresponds to the current trunk? Also, what branches will be
> I would also like to see instructions of checking out and composing a
> monolithic Boost distribution, possibly with (or without) only
> selected libraries.
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.
cmake -P forward_headers.cmake
> 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?
Not automatically today, with the current build system. After a switch
to cmake, yes. That will eventually be something like:
ryppl develop http://ryppl.github.com/feeds/boost/ This command has already been implemented for cmake-enabled boost (and
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk
recently broke because of changes in the dependency structure but will
be repaired shortly).
BoostPro Computing Software Development Training
http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
This command has already been implemented for cmake-enabled boost (and