Hi Xavier,
That worked like a charm!
Thanks very much.
Thanks too to Craig for the link. I had not seen that before.
On 12/16/2018 6:15 PM, Xavier Besseron wrote:
Hi Donald,
For my project, I do it this way.
In my CMakeLists.txt, I first set the variable BUILDNAME in cache
before calling `include(CTest)`.
#defineBUILDNAME,usedtosubmitjobstoCDash
set(BUILDNAME"Whatever you want"CACHESTRING""FORCE)
#ThismustbecalledafterSITEandBUILDNAMEvariablesareset
include(CTest)
I hope this will work for you.
Best regards,
Xavier
On Sun, Dec 16, 2018 at 9:22 PM Craig Scott <craig.sc...@crascit.com
<mailto:craig.sc...@crascit.com>> wrote:
On Mon, Dec 17, 2018 at 6:41 AM Donald MacQueen [|]
<dm...@instantiations.com <mailto:dm...@instantiations.com>> wrote:
I want to do something like set(CTEST_BUILD_NAME
{CMAKE_SYSTEM_NAME}_someLocalVariable)
I tried putting this ^^ in CTestConfig.cmake with no luck.
I searched the docs and the archives from 2014 to the present and
nothing jumped out at me.
2) Is there a list of what can be set/used in CTestConfig.cmake?
The variables are not all collected together conveniently, but the
Dashboard Client section
<https://cmake.org/cmake/help/latest/manual/ctest.1.html#dashboard-client-configuration>
of the ctest command does list the supported variables associated
with each command. It would seem like setting CTEST_BUILD_NAME
should work based on those docs, so perhaps if you could point us
as a minimal complete example which demonstrates your problem,
that might give more clues as to what's happening for you.
--
Craig Scott
Melbourne, Australia
https://crascit.com
New book released: Professional CMake: A Practical Guide
<https://crascit.com/professional-cmake/>
-----------------------------------------------------------------------------------
--
Dr Xavier BESSERON
Research Scientist
FSTC, University of Luxembourg
Campus Belval, Office MNO E04 0415-040
Phone: +352 46 66 44 5418
http://luxdem.uni.lu/team/xbesseron/
--
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
