Hi all
I've just had a problem caused by an upgrade of my system files (in this
particular case: boost). Rebuilding our software didn't correctly rebuild
those files that depend on the updated boost files. (I'm using CMake 3.9
with make on Ubuntu 16.04)
Checking a bit more carefully it appe
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 `in
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)`.
# define BUILDNAME, used to submit jobs to CDash
set(BUILDNAME "Whatever you want" CACHE STRING "" FORCE)
# This must be called after SITE and BUIL
When running tar via CMake (in order to use cross-platform work-ability and
what not) it'd be great to have a progress bar of any sort.
It's awkward to wait 30-60 minutes for file untarring with absolutely 0
information. I'm not aware of any way to do this through CMake directly,
only alternative
On Mon, Dec 17, 2018 at 6:41 AM Donald MacQueen [|] <
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 th
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 CTestCo
