Hi David,
thanks for the clarification. I set ${PROJECT_NAME} and ${SOURCE_DIR} to the
appropriate name, but it changes from script to script (there is one script for
every packet I create, so I only showed the code, that is used by all
projects.)
I am actually not working full time on this j
Hi again,
I am doing something wrong here, but what:
-- snip script.cmake ---
SET ( CTEST_PROJECT_NAME ${PROJECT_NAME} )
SET ( CTEST_BINARY_DIRECTORY ${SOURCE_DIR}/build )
SET ( CTEST_SOURCE_DIRECTORY ${SOURCE_DIR} )
SET ( CTEST_CMAKE_GENERATOR "Unix Makefiles" )
SET ( CTEST_ENVIRONME
Hi,
Ok, adding CTEST_START(...) in my ctest.cmake script make it a little bt
better. The xml files are created, but not in the usual directory (see
below) and the dart2 server fails parsing them.
Going deeper into the problem, I compared the output of the
Ctest -D Experimental -V
command and what
Alex,
> Unfortunatly, everything goes fine except the submission
> part. The //Testing/ folder is created at the
> configuration time, but the intermediate directory is not
> created and thus, the xml files are not present when Ctest
> try to send them.
Which intermediate directory? Please gi
Hi guys,
I set up a dart 2 server (java) in a corner, and succesfully managed to send
reports to it using Cmake.
Now I would like to set up some nightly and continuous builds on several
different machines with differents options (libs version, static/debug,
...). For this , I need to go through s
