From: David Abrahams (dave_at_[hidden])
Date: 2006-11-29 16:28:20
Vladimir Prus <ghost_at_[hidden]> writes:
> On Wednesday 22 November 2006 16:42, HERMIER Christophe wrote:
>> When I want to build a project (except for very simple ones),
>> I need to get the relevant versions of various modules from my source
>> control, for example version 2.00 of some in-house library
>> plus version 3.45 of another library
>> and maybe the in-house library uses another one
>> behind the scenes that I need to...
>>
>> I see nothing in the documentation of Boost Build concerning Version
>> Control... Does it mean you consider this out of scope ? or
>> maybe it's in the plans but I did not see ?
>
> I think it's out of scope. I don't understand why obtaining such extra
> libraries is better be done by Boost.Build than by some external script.
> Maybe I'm missing something, though.
There are lots of tools that build and install software that also
download sources or binaries from somewhere. It seems like an
obviously-desirable thing to be able to integrate that transparently
with a build process. For example, you might not want to or be able
to keep a copy of 3rd-party software in your repository. Or you might
have a large repository with many projects and not want users of one
project to have to correctly acquire all the code for its dependencies
before they can build.
-- Dave Abrahams Boost Consulting www.boost-consulting.com