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 so I could set those variables between project(foo LANGUAGES CXX) and enable_language(CUDA), but I'm seeing other issues with that approach.
Any other suggestions? If not, we'll just wrap our cmake invocation in a script to help setup the environment properly for now. Thx! On Tue, Apr 16, 2019 at 1:10 PM Robert Maynard <robert.mayn...@kitware.com> wrote: > 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/CUDAHOSTCXX.html ) or with > CMAKE_CUDA_HOST_COMPILER on the initial configuration of a project. >
-- 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 offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
