On 1/1/2019 4:48 PM, frodak17 wrote:
I'm trying to follow along but you are calling cmake to do the install
and set everything up before you run ctest.
And that the software was already built and packaged separately.
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 project, no make, no compile, no build. Just set a bunch of
variables and run CTest.
I think from what Kyle said I need to migrate(?) this to a script that
can be called from CTest directly, e.g., ctest -D Experimental -S cdash.txt.
Thanks for the reply.
--
Donald [|]
A bad day in [] is better than a good day in {}.
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
