On 2013-08-09 04:43, Yngve Inntjore Levinsen wrote:
Sorry all, I found my mistake. Essentially in the 'ctest -S script' I
moved all CTestTestfile.cmake to a binary directory using
configure_file() instead of file(COPY .. DESTINATION ..). The
configure_file evaluates all ${}, so the ${MESSAGE} was
I downloaded the eval version of Embarcadero C++ 6.60 for Win32
Copyright (c) 1993-2013 Embarcadero Technologies, Inc.
I am not seeing the same results as you for some reason. With CMake
2.8.11 I am getting makefiles that look like this:
foo.lib: CMakeFiles\foo.dir\build.make
@$(CMA
not better
my CMakeLists.txt :
enable_testing()
include(CTest) # don't know if it's necessary
add_test(MyProgramTest ./program)
my CTestCustom.cmake in the build dir :
message(" hello")
set(CTEST_CUSTOM_MEMORYCHECK_COMMAND "/usr/bin/valgrind")
set(CTEST_MEMORYCHECK_COMMAND "/usr/bin/valgrind
On 8/9/2013 2:06 AM, Bo Berglund wrote:
>You might get away with re-running cmake from the command line.
I will try that when I have my test W7 PC on-line again. It has been
hibernated to make room for other virtual machines I need...
cmake --trace in your existing tree should work.
>You