Edward Diener wrote:
You believe that every end user who wants to use a particular Boost library should run a test script just to determine whether or not that library is supported by Boost for the compiler/version which that person uses ?
Every end user who is not sure whether his configuration is supported by a particular library can run the tests. This is generally done by invoking 'bjam' (or 'bjam --toolset=foo' if the default doesn't work) in the directory containing the tests, for example libs/smart_ptr/test. One can also use 'bjam shared_ptr_test' to single out a particular test. The resulting output could've been friendlier, and the whole procedure better documented, of course. In a perfect world typing 'bjam' (or possibly 'bjam show' or something similar) in a test dir would cause an HTML page with the results to be launched in the default browser. :-)