From 7fe36eead17ee1afb9ba26e1e4eb8613b559f71d Mon Sep 17 00:00:00 2001 From: Kevin Rocard Date: Fri, 6 Mar 2015 10:36:40 +0100 Subject: Use ctest for testing Test were enabled with the enable_testing command. Nevertheless this method is very basic. Include CTest, as this cmake utility enables automatic build + test + coverage generation + memchek test (valgrind) + sending report in one command: ```make Experimental``` There are far more features added by this utility, see: http://www.cmake.org/Wiki/CMake/Testing_With_CTest#Dashboards Signed-off-by: Kevin Rocard --- CMakeLists.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'CMakeLists.txt') diff --git a/CMakeLists.txt b/CMakeLists.txt index 696e4a0..fcef282 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -45,7 +45,10 @@ add_subdirectory(remote-processor) add_subdirectory(remote-process) -enable_testing() +include(CTest) +# Ctest requires its configuration to be placed at the build root +configure_file(CTestCustom.cmake ${CMAKE_BINARY_DIR} COPYONLY) + add_subdirectory(test/test-platform) add_subdirectory(test/test-fixed-point-parameter) -- cgit v1.1