[cmake-developers] Python bindings for CTest

Hi, I have created some Python bindings for CTest. The goal was to create an easy way for Python projects that I work with to be able to wrap their Python compilation log (if there was one), dynamically generate CTests and/or wrap their existing testing commands, do any additional testing

Re: [CMake] CopyOfCMakeCache.txt

Hi Frank, What version of CMake are you running (cmake --version) and what is are you running on? Is this on the Windows Subsystem for Linux? Older CMake versions had similar trouble there that was resolved with more recent releases. - Chuck On Thu, Oct 18, 2018, 17:04 Jean-Christophe

Re: [CMake] CopyOfCMakeCache.txt

Hi Frank, Out of curiosity, did you explicitly pass CMAKE_SYSTEM_NAME variable when configuring your project ? Jc On Wed, Oct 17, 2018 at 6:38 PM Frank Tocci wrote: > Hello, > > I was using the CMake GUI when I came across the following message: > > System is unknown to cmake, create: >

Re: [CMake] ctest_submit CDASH_UPLOAD causes "Not a valid project" error on a valid project

Discussion continues here: https://github.com/Kitware/CDash/issues/736 -- 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

[CMake] Cross-compilation, CMake and Symlinks

So I'm using this guide to cross-compile OpenCV for Raspberry Pi: https://visualgdb.com/tutorials/raspberry/opencv/build/ I'm doing that mainly because building anything on RPi is much slower than on Windows, and because I need the remote debugging tools of Visual Studio. Everything worked as

Re: [cmake-developers] Generalized verbose option for cmake --build.

Am Donnerstag, 18. Oktober 2018, 17:48:28 CEST schrieb Ray Donnelly: > Hi CMake developers, > > Why do I need to know the necessary verbose flag to make each back-end > that cmake --build calls emit more information? If forces my build > script to switch on the platform in a really ugly way for

Re: [cmake-developers] Generalized verbose option for cmake --build.

On 10/18/2018 11:48 AM, Ray Donnelly wrote: > Why do I need to know the necessary verbose flag to make each back-end > that cmake --build calls emit more information? If forces my build > script to switch on the platform in a really ugly way for something > I'd consider a very important feature

[cmake-developers] Generalized verbose option for cmake --build.

Hi CMake developers, Why do I need to know the necessary verbose flag to make each back-end that cmake --build calls emit more information? If forces my build script to switch on the platform in a really ugly way for something I'd consider a very important feature (you already hardcode various

[Cmake-commits] CMake branch, release, updated. v3.13.0-rc1-26-g09daee0

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 09daee07806a75e98afa2a80472de7909c961476 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.13.0-rc1-147-g1771ec8

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 1771ec85b6475c10566026ad7813eb74f732d507 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.13.0-rc1-142-gcb5015f

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via cb5015fb9f91a062fc1c92b698833ee84a71ea50 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.13.0-rc1-23-g2646fd8

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 2646fd8e03869e2254514f43b0c2a07d89c26076 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.13.0-rc1-137-g5b47557

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 5b47557c82c24e916c7926d210c9b72ad39c9d2e (commit) via

[CMake] ctest_submit CDASH_UPLOAD causes "Not a valid project" error on a valid project

Hi, I'm trying to use 'ctest_coverage_collect_gcov(TARBALL gcov.tar)' along with 'ctest_submit(CDASH_UPLOAD gcov.tar CDASH_UPLOAD_TYPE GcovTar)' to upload gcov files to our cdash server. Although this succeeds to upload "normal" results to the server, ctest_start(${CTEST_DASHBOARD_TYPE})