Skip to content
Snippets Groups Projects
Forked from CMake / CMake
21757 commits behind the upstream repository.
  • Brad King's avatar
    4c7cc264
    Tests: Restore NVCC-specific CUDA tests · 4c7cc264
    Brad King authored
    In commit a653ca95 (Tests: Update CUDA tests to work with Clang,
    2020-03-27) some tests were conditioned using `CMAKE_CUDA_COMPILER_ID`.
    That is not defined when configuring CMake itself, so it accidentally
    turned off NVCC-specific CUDA tests altogether.  Convert the conditions
    to check `CMake_TEST_CUDA` for `Clang` instead.  That option is added
    explicitly to builds where we want the tests to run, so we can set it to
    a value indicating the CUDA compiler vendor.
    
    In commit a653ca95 (Tests: Update CUDA tests to work with Clang,
    2020-03-27) the NVCC-specific `CudaOnly.GPUDebugFlag` test was
    accidentally broken by removing a space when appending `-G` to the CUDA
    flags.  This was covered by the test not running.  Restore the space.
    
    Fixes: #20727
    4c7cc264
    History
    Tests: Restore NVCC-specific CUDA tests
    Brad King authored
    In commit a653ca95 (Tests: Update CUDA tests to work with Clang,
    2020-03-27) some tests were conditioned using `CMAKE_CUDA_COMPILER_ID`.
    That is not defined when configuring CMake itself, so it accidentally
    turned off NVCC-specific CUDA tests altogether.  Convert the conditions
    to check `CMake_TEST_CUDA` for `Clang` instead.  That option is added
    explicitly to builds where we want the tests to run, so we can set it to
    a value indicating the CUDA compiler vendor.
    
    In commit a653ca95 (Tests: Update CUDA tests to work with Clang,
    2020-03-27) the NVCC-specific `CudaOnly.GPUDebugFlag` test was
    accidentally broken by removing a space when appending `-G` to the CUDA
    flags.  This was covered by the test not running.  Restore the space.
    
    Fixes: #20727
CMakeLists.txt 757 B