|
|
Boost Testing : |
From: Robert Ramey (ramey_at_[hidden])
Date: 2005-02-21 11:48:18
All the serialization tests fail with all CW versions.
Only now have I seriously investigated this.
a) Darwin -cs 9.3
This is something I can address and have checked in a change
b) windows cw 9.4
These are all failing with the same problem
http://www.meta-comm.com/engineering/boost-regression/developer/output/sslap
eta-bin-boost-libs-serialization-test-test_array_binary_archive-test-cw-9_4-
debug-threading-multi.html
### mwcc Compiler:
# File: ..\libs\serialization\src\xml_oarchive.cpp
# ---------------------------------------------------
# 16: #include <boost/archive/xml_oarchive.hpp>
# Error: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# the file 'boost/archive/xml_oarchive.hpp' cannot be opened
etc.
This looks to me like an issue with the local test setup. On the other
hand, it seems that other libraries are passing on this test platform. I
can't imagine what the issue is here? Could it be a quesion of <include> vs
<sysinclude> or ?. Any suggestions would be appreciated.
c) windows cw 8.3
http://www.meta-comm.com/engineering/boost-regression/developer/output/metac
omm-bin-boost-libs-serialization-test-test_array_binary_archive-test-cw-8_3-
debug-runtime-link-static-threading-multi.html
call "C:\Program Files\Metrowerks\CodeWarrior\Other Metrowerks
Tools\Command Line Tools\cwenv.bat" -quiet
set "ERRORLEVEL="
mwcc -c -lang c++ -DBOOST_LIB_DIAGNOSTIC=1 -maxerrors 5 -warnings
on -maxwarnings 20 -nowraplines -g -O0 -inline off -cwd include -warnings
nounusedexpr,nounused -runtime smd -DNOMINMAX -RTTI on -iso_templates on
"-IC:\Users\Administrator\boost\main\results\bin\boost\libs\serialization\bu
ild" -I- "-IC:\Users\Administrator\boost\main\boost" -o
"C:\Users\Administrator\boost\main\results\bin\boost\libs\serialization\buil
d\libboost_serialization.lib\cw-8_3\debug\runtime-link-static\threading-mult
i\xml_oarchive.obj"
"C:\Users\Administrator\boost\main\boost\libs\serialization\build\../src/xml
_oarchive.cpp"
That is, fails with no message what so ever!!! I might suspect that is
could be related to the fact that the test Jamfile sets <build>no for the
dynamic build - but really I don't know
Any insight to these would be much appreciated.
Robert Ramey