|
From: Luigi B. <lui...@gm...> - 2013-03-04 16:08:10
|
Sorry, what are you using on Linux? libboost_unit_test_framework.so should have been added to the makefile options by configure. Also, <boost/test/unit_test.hpp> is already included in test-suite/utilities.hpp, which is included by all the cpp files in the test suite. Luigi On Mon, Mar 4, 2013 at 4:24 PM, cf16-2 <cf1...@gm...> wrote: > on linux I had to add > >> libboost_unit_test_framework.so > > to the Linker->Libraries and #include <boost/test/unit_test.hpp>. > > #define BOOST_MESSAGE( M ) BOOST_TEST_MESSAGE( M ) > > is already present in test/test_tools.hpp. > on windows I have different #defines and this is not present, so I added it > to the > >> unit_test_log.hpp > > where BOOST_TEST_MESSAGE is defined (in boost files to avoid same issue > again in the case of other applications using BOOST_MESSAGE). BOOST_MESSAGE > issue resolved but still can't default initialize > const void* = boost::test_tools::check_is_close > and void* = boost::test_tools::check_is_small > > > > -- > View this message in context: http://quantlib.10058.n7.nabble.com/BOOST-MESSAGE-undefined-tp14086p14097.html > Sent from the quantlib-dev mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > QuantLib-dev mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-dev |