CMakeEmulateMakeCheck: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
(Initial version)
 
m (Fixed typo)
Line 13: Line 13:
To add a test program <tt><testprog></tt>, use the following commands
To add a test program <tt><testprog></tt>, use the following commands


  add_executable(<testprog> EXCLUDE_FROM ALL ...)
  add_executable(<testprog> EXCLUDE_FROM_ALL ...)
  add_test(<testprog> <testprog>)
  add_test(<testprog> <testprog>)
  add_dependencies(check <testprog>)
  add_dependencies(check <testprog>)

Revision as of 15:31, 25 March 2009

How to emulate GNU Autotools 'make check'

Those of you familiar with the GNU Autotools probably know that the all target in a Makefile generated by autoconf/automake does not cause a (re)build of your test programs (assuming you've listed them as check_PROGRAMS). This is IMHO a very nice feature, because the normal build is not bogged down by the compilation of many test programs, or worse, comes to a grinding halt due to a compilation error in one of the test programs you didn't have time to fix yet. When the time has come to run your test suite, you simply type make check and your test programs will be (re)build and run.

This feature can be emulated in CMake.

Define a custom target

First you need to define a custom target check. You only need to do this once, so doing this in your toplevel CMakeLists.txt file is probably a good idea.

add_custom_target(check COMMAND ${CMAKE_TEST_COMMAND})

Add a test program

To add a test program <testprog>, use the following commands

add_executable(<testprog> EXCLUDE_FROM_ALL ...)
add_test(<testprog> <testprog>)
add_dependencies(check <testprog>)

The option EXCLUDE_FROM_ALL is essential here; it causes <testprog> to be ignored when the all target is built.

Note

If you organize all your test programs in one directory, you can use the EXCLUDE_FROM_ALL option with the add_subdirectory command. That way, you don't need to specify this option with every add_executable command.