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

Re: [CMake] Boost 1.70.0 -- FindBoost issues? No linker libraries found (Mateusz Loskot)

Thank you so much, this works perfectly. > > -- Forwarded message -- > From: Mateusz Loskot > To: cmake@cmake.org > Cc: > Bcc: > Date: Tue, 16 Apr 2019 01:10:44 +0200 > Subject: Re: [CMake] Boost 1.70.0 -- FindBoost issues? No linker libraries > found > On Tue, 16 Apr 2019 at 01:

[CMake] Linked Imported Library in Visual Studio Showing NOTFOUND

Hi All, I'm trying to debug an issues where an imported shared library is showing up in the linker command as not found, but within the CMake generation the target seems to exist. # CMakeLists.txt include(bar.cmake) add_library(foo SHARED) if(TARGET bar) target_link_libr

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 C

Re: [CMake] CXX and CUDACXX

Thx for the info. Since CXX and CUDA are defined together in the project() command, I don't see a way to inject code to use the CXX compiler if no CUDAHOSTCXX or CMAKE_CUDA_HOST_COMPILER is given without replicating the CXX search. I tried moving CUDA out to an enable_language(CUDA) call instead s

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 ( https://cmake.org/cmake/help/v3.12/envvar/CUDAHOST

[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 proj

[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 passing

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: >

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: > > fixture_setup

[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, I'v