summaryrefslogtreecommitdiffstats
path: root/Source/cmConvertMSBuildXMLToJSON.py
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2024-07-17 15:33:29 (GMT)
committerBrad King <brad.king@kitware.com>2024-07-17 15:42:31 (GMT)
commita9210a0c02dd8cc1325d2cbb5eb53e29276f7d4a (patch)
tree86359f486acba42581d01c4f4446b9672a516097 /Source/cmConvertMSBuildXMLToJSON.py
parent3b2ef9b54ca91ed9e0be2680558021b3d000a2ea (diff)
downloadCMake-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