-
Notifications
You must be signed in to change notification settings - Fork 344
Host: introduce GetSDKPath
extension point for Windows
#6736
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
Conversation
@swift-ci please test |
I still think that it is a bit odd as we are saying "SDKPath" for Windows, except that is entirely unclear what that means - Windows SDK? Swift SDK? Oculus SDK? Something else? In any case, I've posted https://reviews.llvm.org/D149397 that we can decide if we want to go down that route. With the introduction of |
Partially completed in #6746. Once we get that merged, I can pull out the actual changes to support the SDK on Windows from this. Leaving this open until then. |
8ebae86
to
9b15210
Compare
@swift-ci please test |
@swift-ci please test Windows platform |
Introduce a new extension point to allow a host to specify a SDK path. On Windows, there is the default global SDK path which is identified by the `SDKROOT` environment variable. Wire this into the process to construct the proper search paths for the Swift module when debugging.
@swift-ci please test |
@swift-ci please test Windows platform |
Introduce a new extension point to allow a host to specify a SDK path. On Windows, there is the default global SDK path which is identified by the
SDKROOT
environment variable. Wire this into the process to construct the proper search paths for the Swift module when debugging.