[Boost-testing] Re: compiler status program

From: Robert Ramey (ramey_at_[hidden])
Date: 2004-12-03 11:29:53

Hmmm - what I want to do on my local machine is build a group of variants
(<target>debug/release, <libtype>lib/dll, etc and have all the results in a
table. Looking at the test results, it seems there is only one variant per
test-compiler.  Am I missing something here?

Robert Ramey

"Aleksey Gurtovoy" <agurtovoy_at_[hidden]> wrote in message
news:cooijp$bhn$1_at_sea.gmane.org...
> Robert Ramey writes:
> > "Aleksey Gurtovoy" <agurtovoy_at_[hidden]> wrote in message
> > news:comvth$npt$1_at_sea.gmane.org...
> > > Robert Ramey writes:
> > > > I use the compiler status program to build a local html file with my
> > > > test results.
> > > >
> > > > It currently builds one line per test and one line per compiler and
> > > > seems to work just fine.
> > > >
> > > > Is there any possibility it might be altered so that it include a
column
> > > > for each compiler/build variant?  This would be very useful to me.
> > >
> > > Robert,
> > >
> > > I'm afraid compiler_status is a legacy tool that we are not interested
in
> > > maintaining of. Unless there is a reason why you cannot use/install
Python
> > > or xsltproc, I'd strongly recommend to switch over to the XSL-based
> > > reporting tools.
> > >
> >
> > would that give me what I want?
>
> Unless we broke something recently, they handle build variants
automatically,
> that is, the variants are all folded into a single correspondingly colored
> compiler/test result cell, by clicking on which you can get the details of
all
> the failures (if any).
>
> --
> Aleksey Gurtovoy
> MetaCommunications Engineering