diff options
| author | Brad King <brad.king@kitware.com> | 2016-01-11 18:44:11 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2016-01-11 18:44:11 (GMT) |
| commit | a57caf7eecdfe61e4ac5f63b145fc9269610f3f0 (patch) | |
| tree | 21fa4585ab0bc896d4638359616b77125e9c8657 /CTestCustom.cmake.in | |
| parent | ad594de8cc9c4063830df58453b0679c209ff4d8 (diff) | |
| download | CMake-a57caf7eecdfe61e4ac5f63b145fc9269610f3f0.zip CMake-a57caf7eecdfe61e4ac5f63b145fc9269610f3f0.tar.gz CMake-a57caf7eecdfe61e4ac5f63b145fc9269610f3f0.tar.bz2 | |
VS: Fix Windows 10 SDK version selection (#15831)
In commit v3.4.0-rc1~5^2~1 (VS: Add support for selecting the Windows 10
SDK, 2015-09-30) we added Windows 10 SDK selection choosing the most
recent SDK that is not newer than the target version. This is backward
because it should be up to the application code to not use APIs newer
than the target version. It is up to the build system to provide a SDK
that has at least the APIs expected to be available for the target
version. Furthermore, since the default target version is the host
version of Windows, the old approach breaks when the only SDK available
is for a newer version of Windows.
Fix this by always selecting a Windows 10 SDK if one exists. Use the
SDK for the exact version if is available. Otherwise use the latest
version of the SDK available because that will have at least the APIs
expected for the target version.
Diffstat (limited to 'CTestCustom.cmake.in')
0 files changed, 0 insertions, 0 deletions