diff options
author | Brad King <brad.king@kitware.com> | 2024-07-17 15:33:29 (GMT) |
---|---|---|
committer | Brad King <brad.king@kitware.com> | 2024-07-17 15:42:31 (GMT) |
commit | a9210a0c02dd8cc1325d2cbb5eb53e29276f7d4a (patch) | |
tree | 86359f486acba42581d01c4f4446b9672a516097 /Source/cmConvertMSBuildXMLToJSON.py | |
parent | 3b2ef9b54ca91ed9e0be2680558021b3d000a2ea (diff) | |
download | CMake-a9210a0c02dd8cc1325d2cbb5eb53e29276f7d4a.zip CMake-a9210a0c02dd8cc1325d2cbb5eb53e29276f7d4a.tar.gz CMake-a9210a0c02dd8cc1325d2cbb5eb53e29276f7d4a.tar.bz2 |
VS: Restore support for CUDA with no optimization flags
Since commit 67de5b7b82 (VS: Suppress MSBuild default settings affected
by UseDebugLibraries, 2024-02-13, v3.30.0-rc1~538^2~1) we generate an
empty `Optimization` element for the host compiler when there are no C
or C++ optimization flags enabled. The CUDA Toolkit Visual Studio
integration fails with an error if an empty string is inherited from the
host compiler's `Optimization` element. If no CUDA optimization flags
are specified, write an explicit empty `Optimization` element for the
CUDA compiler too.
Fixes: #26144
Diffstat (limited to 'Source/cmConvertMSBuildXMLToJSON.py')
0 files changed, 0 insertions, 0 deletions