diff options
| author | Brad King <brad.king@kitware.com> | 2020-06-18 19:55:18 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2020-06-18 19:58:38 (GMT) |
| commit | a0280801f43770b506b8c621637cc2870db2c8e1 (patch) | |
| tree | 73cae802e6ed1f67afd0a06bcbd43c3191fc71bd /Modules/CMakeFortranCompiler.cmake.in | |
| parent | 90be0916b549e806f6e72eb3ca2d8237a1adf174 (diff) | |
| download | CMake-a0280801f43770b506b8c621637cc2870db2c8e1.zip CMake-a0280801f43770b506b8c621637cc2870db2c8e1.tar.gz CMake-a0280801f43770b506b8c621637cc2870db2c8e1.tar.bz2 | |
CUDA: Fix CMAKE_CUDA_COMPILER_TOOLKIT_ROOT detection in Visual Studio
When using a Visual Studio generator, we do not know the path to
`CMAKE_CUDA_COMPILER` until after the compiler id detection project
extracts it. However, based on the VS toolchain configuration we know
that the compiler id will be NVIDIA, so use that to drive the CUDA
architecture flag logic. After the main compiler id step we know
`CMAKE_CUDA_COMPILER`, so `CMAKE_CUDA_COMPILER_TOOLKIT_ROOT` can then be
computed.
Diffstat (limited to 'Modules/CMakeFortranCompiler.cmake.in')
0 files changed, 0 insertions, 0 deletions