[Boost-build] bjam testing outside of a directory name "test"

From: Robert Ramey (ramey_at_[hidden])
Date: 2007-08-08 18:31:51

When I run a testing Jamfile from a ../libs/serialization/peformance I get 
the following output

Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(don't panic: this is a strictly optional feature).
boost-test(RUN) "serialization/performance/performance_codecvt_null" : 
"libs/serialization/performance/performance_codecvt_null.cpp" 
"libs/serialization/src/codecvt_null.cpp"
boost-test(RUN) "serialization/performance/performance_utf8_codecvt" : 
"libs/serialization/performance/performance_utf8_codecvt.cpp" 
"libs/serialization/src/utf8_codecvt_facet.cpp"
boost-test(RUN) "serialization/performance/performance_iterators_base64" : 
"libs/serialization/performance/performance_iterators_base64.cpp"

However, when I run a testing Jamfile from a ../libs/serialization/ I get 
the following output

Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(don't panic: this is a strictly optional feature).
boost-test(RUN) "serialization/test_polymorphic_text_archive" : 
"libs/serialization/test/test_polymorphic.cpp" 
"libs/serialization/test/test_polymorphic_A.cpp"
boost-test(RUN) "serialization/test_polymorphic_text_warchive" : 
"libs/serialization/test/test_polymorphic.cpp" 
"libs/serialization/test/test_polymorphic_A.cpp"
boost-test(RUN) "serialization/test_polymorphic_binary_archive" : 
"libs/serialization/test/test_polymorphic.cpp" 
"libs/serialization/test/test_polymorphic_A.cpp"
boost-test(RUN) "serialization/test_polymorphic_xml_archive" : 
"libs/serialization/test/test_polymorphic.cpp" 
"libs/serialization/test/test_polymorphic_A.cpp"

Notice that in the first case, the directory name "performance" is in the 
name after the (RUN)
while in the second case, the directory name "test" is not in the same 
place.

This inconsistency ripples through process_jam_log and the xml files that it 
places
in the bin.v2 directories unless everything is a really annoying limitation. 
Which has
taken a long time to track down.  Is there a convenient way to fix this?

Robert Ramey