From: John Maddock (john_at_[hidden])
Date: 2005-12-08 05:38:42
> Indeed. One thing I already proposed in the past: some dummy tests
> to autoconf macros) that make sure a sane configuration / environment
> is available at all. These tests could cover a specific toolchain, or
> some lightweight library-specific code. If these are known as
> dependencies for the rest of the test suite(s), quite a bit of
> computing power (and
> mail bandwidth) could be spared whenever these fail.
Good thinking, all we need is a "hello world" program and make all the tests
dependent upon a successful build of that specific program. Adding a hello
world program to say Boost.Config is pretty trivial, would someone like to
volenteer to hack Boost.Build?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk