Re: [Boost-testing] process_jam_log and compiler_statusproducinginvalid report

Subject: Re: [Boost-testing] process_jam_log and compiler_statusproducinginvalid report
From: Robert Ramey (ramey_at_[hidden])
Date: 2009-03-08 18:12:02

Hmmm, I've been using it continuously on a regular basis for a very long 
time.

On my system using the mks shell I can run:

$
$ pwd
C:/BoostRelease/libs/serialization/test
$ ../../../tools/regression/src/library_test.sh
Usage: ../../../tools/regression/src/library_test.sh <bjam arguments>
Typical bjam arguements are:
  --toolset=msvc-7.1,gcc
  variant=debug,release,profile
  link=static,shared
  threading=single,multi
  -sBOOST_ARCHIVE_LIST=<archive name>
$ ../../../tools/regression/src/library_test.sh --toolset=msvc-7.1

When the whole thing ends, I get a table which looks simlar to 
http://www.rrsd.com/software_development/boost/library_status.html

Robert Ramey

Steven Solie wrote:
> On 05/03/2009, Robert Ramey wrote:
>> You could try the library_test.sh in tools/regression/src/build. I
>> use it regularly
>
> Tried that tool as well. No luck with the 1.38.0 release.
>
> It gets confused by the subdirectory layout similar to how the
> compiler_status tool does.
>
> --Steven