David Abrahams wrote:
"Robert Ramey" <ramey@rrsd.com> writes:
Actually, it should be easy to use v2's "target alternatives" feature to exclude certain tests from the suite depending on toolset.
The problem is that the the toolset name doesn't reliably convey the needed information. Specifically, there are tests which are pointless to run if the platform doesn't handle wide character i/o. Some versions of gcc implement it - others don't. And I can't figure out how to know with certainty in all cases. What I'm thinking about is more along the lines of the following: There would be a test as part of "config" group which results passes if wide char i/o is supported on the platform. Then, using "dependency" facilty - new in v2 I believe, condition the tests which require wide char i/o on the successful passing of the wide char i/o test. I'm not sure if v2 can be setup for this but this is what I would like to do. In fact, I would like to extend the concept even further. There isn't much point in running serialization tests on say - variant, if the other more basic tests for variant aren't all passing. So I would think it valuable to condition these tests also. All this required investigation and experiment - certainly not something appropriate for a "release" branch.
a couple of demos - fast_archive, portable archive don't pass when auto-linking is used. They conflict with auto-link in a fundamental way
How so?
I forget the details.
That sounds familiar. Don't you write these things down?
Not as much as I should. But in this particular case, some information can be found in the serialization documentation: Reference/Implemenation Notes/Compiler/Library Issues/VC++7.1 Robert Ramey