summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake/NinjaMultiConfig/qt5.cxx
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2020-05-19 18:02:51 (GMT)
committerBrad King <brad.king@kitware.com>2020-05-20 14:48:20 (GMT)
commit4c7cc264af285ec5c12989a8d18a5141a9c0dd68 (patch)
tree65a471b3638809eb233fecbba12b695552733eb8 /Tests/RunCMake/NinjaMultiConfig/qt5.cxx
parentb246dee7db2e7e6fcd2a00c5b2bd6db21045025f (diff)
downloadCMake-4c7cc264af285ec5c12989a8d18a5141a9c0dd68.zip
CMake-4c7cc264af285ec5c12989a8d18a5141a9c0dd68.tar.gz
CMake-4c7cc264af285ec5c12989a8d18a5141a9c0dd68.tar.bz2
Tests: Restore NVCC-specific CUDA tests
In commit a653ca9504 (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 a653ca9504 (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
Diffstat (limited to 'Tests/RunCMake/NinjaMultiConfig/qt5.cxx')
0 files changed, 0 insertions, 0 deletions