Re: [Boost-testing] [iostreams][Beman] what GCC version are yourunning?

From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2005-06-13 08:35:04

Beman Dawes writes:
> Regardless of the name, copying and renaming locally didn't
> work. The regression.py script deleted the file when it unzipped the
> fresh Boost tree.

Yes, it should reside in the same directory as regression.py itself.

>
> Also, depending on the exact toolset name is error prone and requires manual 
> intervention every new compiler version. Too easy for a compiler to be 
> upgraded, but the tool name not updated.
>
> compiler_status used to get the compiler version from the config
> information. That was automatic and reliable. Any idea why it was
> changed?

Well, several reasons:

1) If you run test for two different versions of the same compiler,
   you need custom toolsets anyway.

2) Just version is not enough. In most cases the toolset name also
   needs to encode other important parts of the testing environment.

3) *If* you are not running two different versions of the same
    compiler, you could theoretically pass the necessary info in the
    resulting XML without modifying the toolset name, but that's a
    special case that doesn't seem worthy bothering.

4) BB v.2 was/is coming with something completely different on the
   toolsets side, and the whole thing needs to be considered/revised
   in that light.

-- 
Aleksey Gurtovoy
MetaCommunications Engineering