18 Jul
2008
18 Jul
'08
4:10 a.m.
Doug Gregor wrote:
On Jul 17, 2008, at 4:43 PM, Ilya Sokolov wrote:
Robert Ramey wrote:
[snip]
In short, implementing this would require a different and more intricate trunk testing script. This is simple to state and to describe - but would in practice be somewhat tricky due to the following: a) Library code not found in one directory
I think this is the biggest issue and it prevents many ideas to work. Perhaps, we should solve it first?
We're working on this so-called "modularization" of Boost as part of the Boost-CMake project. Eventually, every library will be contained within a single directory tree, and will describe its dependencies on other libraries.
It is perfectly doable in boost.build also. Does anybody working on it?