I've been trying to run the unit tests for BBv2, after
fixing the
MinGW/MSYS problem. And as it stands, running these tests is
pointless
for me. With reported failures like this:
====
FAILED
path_features : File x/bin/gcc/debug/m.exe not
added as
expected
-------- all changes caused by last build command ----------
Added files :
['x/bin/gcc-mingw_special-3.4.5/debug/m.exe',
'x/bin/gcc-mingw_special-3.4.5/debug/m.o']
Removed files : []
Modified files: []
Touched files : []
====
It makes it useless for anything but the bare install and
setup. Which
as far as I can think no one would have. How hard is it to
make the test
system flexible enough to make the above pass? Or to put it
another
way... Please fix this!
--
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software
.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|