Assuming your using the trunk - you're almost there. This is the exact purpose of library_status. I use it here. Unfortunately, there are a couple of pending issues. a) Its only in the trunk b) It depends upon changes in process_jam_log which are still pending testing c) You can see a sample of the output at www.rrsd.com Robert Ramey eg wrote:

I notice that all the boost libraries have tests associated with them, which can be invoked by bjam somehow.

Can someone tell me how to invoke bjam to run a specific test for a given (single) library, or run the whole suite of tests for the single library? As opposed to running all tests for all libraries.

Alternatively, if you could point me to some docs which describe it, I can take it from there. (I did some searching but have struck out so far).

Thanks _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

on Thu Aug 30 2007, eg <egoots-AT-gmail.com> wrote:

I notice that all the boost libraries have tests associated with them, which can be invoked by bjam somehow.

Can someone tell me how to invoke bjam to run a specific test for a given (single) library, or run the whole suite of tests for the single library? As opposed to running all tests for all libraries.

The easy way is to go into the $BOOST_ROOT/libs/<libraryname>/test directory, and run bjam there. If you want to run just one test, supply the test name on the bjam command line. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com