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