Roland Schwarz wrote:
3) Failing test tests: This is a DLL issue. In file boost/test/test/unit_test_suite_impl.hpp the compiler coplains about base class test_unit not defined, despite it is. The compiler seems to have problems to see this class as defined. Something (possibly templated memebers?) are prohibiting this when the class is flagged as _declspec(dllexport). *) Is this a known issue? *) Can we safely flag these tests as n/a? A comment in libs/test/build/Jamfile.v2 let me believe so.
This one is truely weird: it looks like an obvious compiler issue to me. What happens if we add a build requirement to Boost.Test that only static libraries are supported with msvc-6: something like <toolset>msvc-6.0:<link>static johnmaddock@boost.cvs.sourceforge.net's password: Index: Jamfile.v2 =================================================================== RCS file: /cvsroot/boost/boost/libs/test/build/Jamfile.v2,v retrieving revision 1.10.2.2 diff -u -r1.10.2.2 Jamfile.v2 --- Jamfile.v2 10 Nov 2006 19:59:52 -0000 1.10.2.2 +++ Jamfile.v2 30 Jan 2007 10:03:23 -0000 @@ -11,6 +11,8 @@ <toolset>borland:<cxxflags>-w-8080 # Disable Warning about boost::noncopyable not being exported <link>shared,<toolset>msvc:<cxxflags>-wd4275 + <toolset>msvc-6.0:<link>static + <toolset>msvc-6.5:<link>static : usage-requirements <define>BOOST_TEST_NO_AUTO_LINK=1 <link>shared:<define>BOOST_TEST_DYN_LINK=1 Which seems to be worthwhile applying whatever? Note that it doesn't solve all the issues though: mearly turns compile-time failures to run-time failures :-( John.