Actually that might be enough to handle the wide char issue in my example. To make things nice a clean it would seem that one would need: a) A simple config tests - test_config_wchar_support marked compile passed b) markup set so that "sometimes fails" so its not marked red c) <dependency>test_config_wchar_support Which would help a lot. There would still be an issue tests don't fail untl runtime. I don't know if that would be required. actually I was sort of expecting (hoping) something like <dependency>test_?.run // dependent on successful exectution of test_? which would be a more general and (to me) natural solution. Robert Ramey
compile test_that_compiler_is_good_and_shiny.cpp ;
unit-test a : a.cpp : <dependency>test_that_compiler_is_good_and_shiny ;
If the compile test fails to compile, then 'a' won't be compiled either. We "only" need to make sure that the first test is not added to regression results as "fail".
- Volodya
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost