[CMake] CTest / CDash integration

[Clinton Stimpson]

On Tuesday, April 09, 2013 04:11:06 PM Martin Baute wrote:
> I realize I haven't been all that clear about my intentions.
> 
> I want to keep the amount of configuration files at a minimum.
> Lots of the information that is required for CTest (like config
> settings, source path, binary path etc.) or CDash (server address,
> project name) are already given in CMakeLists.txt, so naturally
> I am looking to keep it all together instead of spreading it over
> a number of different files cluttering my project.

The CDash settings go into the CTestConfig.cmake file and that file resides next 
to the CMakeLists.txt file.  Its in a separate file because one can use 
CTest/CDash without using CMake.

How are the config settings and binary path for CTest already given in the 
CMakeLists.txt file?  Normally, a CMakeLists.txt file does not have a hardcoded 
binary path, nor does it have fixed config settings.  Between different 
computers, I can set a different binary path, and set different config settings.

Because those aren't known in the CMakeLists.txt file, and they can vary 
between machines, a machine specific CTest script can provide that information.

I keep a separate repository for CTest scripts for use by various machines.  
Each machine uses one of the scripts and can get updates to that script before 
getting updates to the source it is going to work on.  I also keep the bulk of 
the CTest script in shared files, and the machine specific scripts have minimal 
code before including a shared script.

> 
> The information available in the documentation is focussing on
> various details, but doesn't really explain the "right" (intended)
> way of putting together a CMake-built project that supports
> uploading CTest results to a CDash server, so I was wondering
> if I was missing something.
> 
> Regards,
-- 
Clinton Stimpson
Elemental Technologies, Inc
Computational Simulation Software, LLC
www.csimsoft.com