[CMake] CTest / CDash integration

[David Cole]

ctest has long been quite "under-documented"

There are some open issues in the bug tracker:

    http://public.kitware.com/Bug/view.php?id=10392
    http://public.kitware.com/Bug/view.php?id=13836

What's needed is someone to go in and do the work to document it well.

Until that happens, your best bet is to ask specific questions here to fill in the gaps...


HTH,
David C


On Apr 10, 2013, at 10:09 AM, Martin Baute <solar at rootdirectory.de> wrote:

> Sorry, but I have to keep complaining about the documentation. Please
> excuse the ranting.
> 
> Just one example from the manual:
> 
>   ctest --build-options: Add extra options to the build step.
>   This option must be the last option with the exception of --test-command
> 
> End of available information.
> 
> I have not been able to figure out which CTEST_* variable these options
> end up in, or how I could make them actually *affect* the build.
> 
> I am also still looking for a reference of variables used by CTest.
> 
> Quite obviously it is required to set both CTEST_SOURCE_DIRECTORY and
> CTEST_BINARY_DIRECTORY in your script, as CTest keeps telling you if you
> try to execute an empty script. I wonder if it wouldn't be easier if CTest
> would assume the current directory as BINARY_DIR and the script directory
> as SOURCE_DIR by default, but that might be just me.
> 
> That I have to set CTEST_COMMAND manually when I obviously just called the
> executable, conveniently passing a working invocation in argv[0]). Strange.
> 
> CTEST_SITE / CTEST_BUILD_NAME constitute the identification sent to the
> CDash server, as I found out perusing some example scripts on the Wiki,
> none of which really explaining what is done. Nice, but why ain't I told
> in plain English?
> 
> As SVN user, I have to set CTEST_CHECKOUT_COMMAND myself (to something
> resembling "svn checkout ${MY_REPOSITORY} ${CTEST_SOURCE_DIRECTORY}".
> Figured it out, works. But apparently CTEST_UPDATE_COMMAND is something
> else entirely, as CTest insists on appending "update --non-interactive"
> on its own accord...
> 
> It is possible to trial & error your way around all this, but I would
> REALLY prefer to have a reference list, telling me which features I might
> be missing, or how I should escape quotation marks and semicolons in a
> -DCMAKE_PREFIX_PATH= statement. Or why a statement that works when given
> as CTEST_CONFIGURE_COMMAND fails when passed in ctest_configure( OPTIONS ).
> 
> Hence, again my question: Is the man page and the half-dozen pages in the
> Wiki really all there is in freely available documentation on CTest?
> 
> Regards,
> -- 
> Martin Baute
> solar at rootdirectory.de
> 
> --
> 
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20130410/36a51760/attachment.htm>