[CMake] CXX and CUDACXX

Hi All, I'd like to understand the expectations with CMake 3.12+ with the following setup. project(foo LANGUAGES CXX CUDA) By default, should the CUDACXX compiler be using the found compiler for CXX for host-side compilation? What I'm seeing is that host-side compilation for CUDA is not

[CMake] ctest // fixtures and --repeat-until-fail

Hello All, Has anybody knows how FIXTURES_SETUP/FIXTURES_CLEANUP should work with --repeat-until-fail option? My expectation, if I requesting a test run for example 10 times, the sequence should be as follows: fixture_setup, then test, then fixture_cleanup repeats 10 times But in practice,

Re: [CMake] ctest // fixtures and --repeat-until-fail

> > On Tue, Apr 16, 2019 at 10:07 PM Sergei Nikulov > wrote: >> >> Hello All, >> >> Has anybody knows how FIXTURES_SETUP/FIXTURES_CLEANUP should work with >> --repeat-until-fail option? >> >> My expectation, if I requesting a test run for example 10 times, the >> sequence should be as follows:

[CMake] Correct use of VS_DEBUGGER_WORKING_DIRECTORY etc.

I’m trying to use the new VS_DEBUGGER_WORKING_DIRECTORY and VS_DEBUGGER_COMMAND properties to facilitate debugging in a CMake-generated Visual Studio project file (in my case Visual Studio 2013). Everything else in my configuration works except this… I’ve noted from ‘regular’ Visual Studio

Re: [CMake] CXX and CUDACXX

The default implementation is to defer to CUDA for selecting what ever host compiler it would like. To make sure that CMake uses the same CXX and CUDACXX compiler you will need to explicitly state that either through the CUDAHOSTCXX env variable (

Re: [CMake] CXX and CUDACXX

I don't have any other suggestions. In general I recommend the script approach or using enable_language(CUDA). The enable_language approach should work, so I am curious what other issues you are seeing. On Tue, Apr 16, 2019 at 2:24 PM Dustyn Blasig wrote: > > Thx for the info. > > Since CXX and

Re: [CMake] How to generate a non-standard platform and non-standard project file with the Visual studio generator

OK, no response yet. I'm not sure if that means this is a problem that isn't interesting to most or if it is a good hard problem that no one knows how to solve. Thinking a little more, I'm starting to lean toward a solution where I have a build_src folder where I put something like the sample

[Cmake-commits] CMake branch, release, updated. v3.14.2-6-g09fba61

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 09fba6146fa726a83cbbccc3d5fb288f7f14f111 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.14.2-731-g2d37678

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 2d3767822662ad3f19190eb5a84b43becdb84a1f (commit) via

[Cmake-commits] CMake branch, master, updated. v3.14.2-732-g8d5eb97

t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 636d332..b7b278b 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 14) -set(CMake_VERSION_PATCH 20190416) +set(CMake_VER