-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WindowsSdkLocator doesn't detect Windows SDK 10 #929
Comments
The current workaround is to either:
Option 1 may have side effect and undefined behavior regarding breaking changes made the Windows API between 8.1 and 10 or missing feature as you will be targeting Windows 8.1 feature set. |
This could be fixed by making WindowsSdkLocator working in the same way as DefaultUrctLocator and abstracting both to a common WindowsLocator. |
I've just hit the same bug. 13:23:37.595 [DEBUG] [org.gradle.nativeplatform.toolchain.internal.msvcpp.DefaultWindowsSdkLocator] Ignoring candidate Windows SDK directory C:\Program Files (x86)\Windows Kits\10 as it does not look like a Windows SDK installation. |
@lacasseio @eljobe can this be moved to gradle-native? |
This may help someone (workaround 1 from @lacasseio) : |
This is fixed in #4414. I'm going to close this issue. Please open a new issue if you run into any further problems with Visual Studio or Windows SDK discovery. |
Expected Behavior
Gradle should detect and use the Windows SDK 10 if installed or directly pass as a candidate.
Current Behavior
Gradle doesn't detect and use Windows SDK 10. On a clean machine (possibly only Windows 10) with a fresh install of Visual Studio 2015, Gradle fail to build any application that requires access to the Windows SDK (for example
kernel32
).Context
This is a bit tricky to solve as with Windows SDK 10, Microsoft started versioning the
include
andlib
in relation to move toward the Universal C Runtime.Steps to Reproduce (for bugs)
On a fresh Windows 10 machine with only Visual Studio 2015 install try to build CUnit sample.
The text was updated successfully, but these errors were encountered: