Am 09.04.2013 16:29, schrieb Clinton Stimpson:
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.
Wrong wording, sorry. They are, after successful configuration, in the
CMakeCache.txt. Now I'm facing two options regarding CTest:
- Doing incremental builds only, omitting information e.g. on the
number
of compiler warnings from the data sent to CDash.
- Wiping the binary directory clean - including the platform-specific
configuration.
Now, I could set up a CTest script that does the CMake configuration
for me. As it's platform specific, it would have to have lots of if /
else constructs, duplicating most of what CMakeLists.txt does. OR I
could create a CTestScript.cmake.in and forward the necessary settings
from CMakeLists.txt (using configure_file()).
All this strikes me as somehow needlessly complicated when lots of the
necessary settings *could* be handled by the code that I add when I say
"include( CTest )". Add to that the somewhat lackluster documentation
of CTest itself (no variable docs, several command-line options under-
documented etc.), and I get the feeling that I'm simply *missing*
something, like, a crucial page in the Wiki or an integration guide
or somesuch. From what I've seen from the CMake / CTest / CDash trinity
so far, it's really big on "out of the box" functionality, which is why
I find this issue so confusing.
Regards,
--
Martin Baute
[email protected]
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
