[Cmake-commits] CMake branch, master, updated. v3.13.1-563-gf92e953

t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 9d65885..8844d44 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 13) -set(CMake_VERSION_PATCH 20181204) +set(CMake_VER

[cmake-developers] A dashboard that reveals a ctest issue on Windows when there are no tests

Three dashboards for PLplot submitted today at had a build warning concerning ctest. For example, contained Build Warnings (1) *** WARNING non-zero return value in ctest from:

Re: [CMake] Build and run an external project

Yes, I'm able to do it manually using the custom target I created with add_custom_target, by editing the debug properties to get a runnable object. I was hoping that the VS_DEBUGGER_COMMAND used for add_executable would also work with the add_custom_target, but alas they don't. On Tue, Dec 4,

[CMake] Failing to set VS_DEBUGGER_* on target added via add_custom_target.

Hi, I - being new to CMake - somehow fail to set VS_DEBUGGER_* property values on a project added via add_custom_target(). The settings of those property values seem to be lost and not written to any .vcxproj file. Doing the same to a target added via add_executable() works on the other hand

Re: [CMake] New version forces rebuild all?

Le mar. 4 déc. 2018 à 11:44, Andy a écrit : > Problem are still. > Alone make also give me problems. > Do you have stripped down project example? > Ninja is replacement od cmake or make? > ninja (https://ninja-build.org/) is make replacement for which there is a CMake generator.