diff options
| author | Brad King <brad.king@kitware.com> | 2020-03-25 19:25:39 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2020-03-26 12:18:25 (GMT) |
| commit | f3d7a1501003ab9582b94639b06d19feed107f2f (patch) | |
| tree | 2b7ebddd7808e5bad93c629bac15e60cc3daffa4 /Modules/CMakeDetermineRCCompiler.cmake | |
| parent | e3185e3d1b92a95c18f22f70b3cef6944dd019eb (diff) | |
| download | CMake-f3d7a1501003ab9582b94639b06d19feed107f2f.zip CMake-f3d7a1501003ab9582b94639b06d19feed107f2f.tar.gz CMake-f3d7a1501003ab9582b94639b06d19feed107f2f.tar.bz2 | |
VS: Fix ClangCL toolset compiler path detection
Prior to commit 3c125c6de0 (VS: Support Visual Studio Clang Toolkit
identification, 2019-12-03, v3.17.0-rc1~341^2) using `-T ClangCL`
would work but `CMAKE_{C,CXX}_COMPILER` would be detected as `cl.exe`
even though `clang-cl.exe` is the actual compiler. That commit
attempted to fix the detection by using `$(ClangClExecutable)`
as we do for LLVM-distributed toolsets, but that is not actually
defined. Instead, look for `$(CLToolExe)` in the `PATH`.
Fixes: #20504
Diffstat (limited to 'Modules/CMakeDetermineRCCompiler.cmake')
0 files changed, 0 insertions, 0 deletions