Hi Petr, 2012/1/16 Petr Machata <pmach...@redhat.com>
> I was trying to run tests in the CMake-ified boost, and found that many > tests fail even to configure. > [...] I gave up after phoenix. > For sure, you have courage! I gave up earlier than that... Hmm, so, is this a known thing? Perhaps I'm just missing some magic > that makes it all work. I know cmake boost is in a lot of flux, so > chances are this area just needs some work. > Dave Abrahams has recently summed up the status of (modularised) Boost.CMake: https://svn.boost.org/trac/boost/wiki/CMakeModularizationStatus In particular, there is a link with the official dashboard for the standard (non-CMakeified) Boost: http://www.boost.org/development/tests/trunk/developer/summary.html As you will see, there are still a few failing tests. At least, it should give some hints on which parts are expected to compile, fail to compile, run successfully or simply fail. The tests are detailed for each given component. For instance, for IO-Streams: http://www.boost.org/development/tests/trunk/developer/iostreams.html When the test fails, there are some debugging output: http://www.boost.org/development/tests/trunk/developer/output/Sandia-gcc-4-5-2-boost-bin-v2-libs-iostreams-test-newline_test-test-gcc-4-5-2-debug.html Note that the robot performing the tests for modularised Boost provide also some details: http://bbot.boostpro.com/waterfall?show_events=true&builder=Boost-gcc-linux-Integration&reload=none That does not answer exactly your questions, but it gives some food for thoughts, doesn't it? Cheers Denis
_______________________________________________ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
