[CMake] Test sources
Ken Martin
ken.martin at kitware.com
Mon Feb 19 10:08:08 EST 2007
We have a test for CREATE_TEST_SOURCELIST in CMake/Tests/TestDriver and it
does not use a full path to the tests and it is passing on the dashboard.
Perhaps you specified the path to the test source files as a full absolute
path?
Ken Martin PhD
Kitware Inc.
28 Corporate Drive
Clifton Park NY 12065
518 371 3971
-----Original Message-----
From: cmake-bounces+ken.martin=kitware.com at cmake.org
[mailto:cmake-bounces+ken.martin=kitware.com at cmake.org] On Behalf Of Pascal
Fleury
Sent: Sunday, February 18, 2007 6:18 PM
To: cmake at cmake.org
Subject: [CMake] Test sources
Hi CMakers,
I am trying to use the CREATE_TEST_SOURCELIST approach to test some existing
CppUnit tests. My plan was to have the functions that CTest expects ( the
foo(int,char**) for test in file 'foo.cpp' ) be generated, each of them
calling the suite from the CppUnit (basically testing a complete class).
I have noticed that, contrary to the documentation (online, man page and the
book) the function that needs to be present is not 'foo()' for file foo.cpp,
but something like '_full_absolute_path_to_my_project_test_foo(int,
char**)'.
Does CREATE_TEST_SOURCELIST rewrite all test source and replace the expected
function with a unique one ?
Has anybody any experience in using CppUnit with CMake ?
--paf
_______________________________________________
CMake mailing list
CMake at cmake.org
http://www.cmake.org/mailman/listinfo/cmake
More information about the CMake
mailing list