on Wed May 09 2007, Doug Gregor <dgregor-AT-osl.iu.edu> wrote:
The only one I'm not sure about is:
- It should be possible to build multiple variants of multiple targets with multiple compilers from a single build command.
I think this particular requirement is actually a problem itself: it only really helps Boost developers that want to quickly test on a couple of compilers. The majority of users will typically use Boost one just one compiler (especially those users picking up Boost for the first time, who are most put-off by a complicated build system). It's just as easy, if not easier, to keep separate build trees (one per compiler) rather than cram everything into a single build tree.
I've been thinking the same thing myself for some time. However, for me, the ability to quickly test on a whole mess 'o' compilers has been crucial to my ability to build portable C++ libraries. So IMO it's still important to cover that use case somehow. Maybe that ends up being done with scripts? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com