Hi Kyle & Donald,
ctest scripting is documented in here as well:
https://cmake.org/cmake/help/v3.13/manual/ctest.1.html#ctest-script
Since this is generated from in-source documentation:
https://github.com/Kitware/CMake/blob/master/Help/manual/ctest.1.rst
may be an explanation on how to use ctes
On Wed, 2019-01-02 at 12:01 -0500, Donald MacQueen [|] wrote:
> I looked at the example of Using ctest and cdash without cmake
> (https://gitlab.kitware.com/cmake/community/wikis/doc/ctest/Using-CTE
> ST-and-CDASH-without-CMAKE#steercmake)
> and I think I will try to go in that direction.
Donald
Hi Kyle,
I looked at the example of Using ctest and cdash without cmake
(https://gitlab.kitware.com/cmake/community/wikis/doc/ctest/Using-CTEST-and-CDASH-without-CMAKE#steercmake)
and I think I will try to go in that direction.
Part of my confusion is that I inherited this from a former emplo
On Tue, 2019-01-01 at 16:55 -0500, Donald MacQueen [|] wrote:
> No. CMakelists.txt does nothing but download the correct installer
> (32 or 64 bit) from our server, set a bunch of variables, and then
> run CTest. I invoke the InstallShield installer from a command line
> in a CTest.
> There is no
