Re: [boost] Directory structure not quite right yet?

Subject: Re: [boost] Directory structure not quite right yet?
From: Peter Dimov (lists_at_[hidden])
Date: 2015-01-04 10:48:10

Bjørn Roald wrote:

> What is the end goal?

That was, and remains, a very good question.

The end goal is a tool 'bpm' that can do this:

D:\tmp3>bpm install filesystem
bpm: installing module 'filesystem'
bpm: installing module 'assert'
bpm: installing module 'config'
bpm: installing module 'core'
bpm: installing module 'detail'
bpm: installing module 'functional'
bpm: installing module 'io'
bpm: installing module 'iterator'
bpm: installing module 'range'
bpm: installing module 'smart_ptr'
bpm: installing module 'static_assert'
bpm: installing module 'system'
bpm: installing module 'type_traits'
bpm: installing module 'mpl'
bpm: installing module 'preprocessor'
bpm: installing module 'function'
bpm: installing module 'function_types'
bpm: installing module 'integer'
bpm: installing module 'optional'
bpm: installing module 'typeof'
bpm: installing module 'utility'
bpm: installing module 'concept_check'
bpm: installing module 'conversion'
bpm: installing module 'tuple'
bpm: installing module 'array'
bpm: installing module 'regex'
bpm: installing module 'align'
bpm: installing module 'predef'
bpm: installing module 'throw_exception'
bpm: installing module 'bind'
bpm: installing module 'move'
bpm: installing module 'build'
bpm: the following libraries need to be built:
  filesystem regex system
bpm: (use ./b2 to build)
bpm: recreating header links

which should be self-explanatory.

When it says "installing module 'foo'", it means "downloading libs/foo" 
(except for build, where it downloads tools/build and a few other files.)

How does it figure out what modules to install? By looking at the output of 
boostdep --track-sources --list-dependencies.