-
Notifications
You must be signed in to change notification settings - Fork 10.6k
[Target Info] Compute resource-directory relative to the SDK on non-Darwin targets #72409
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This just fixes the narrow problem of passing the right path for the Swift core modules back to
swift-driver, but I raised a larger concern in the issue that motivated this pull, swiftlang/swift-driver#1562, that theswift-frontendis not looking in a passed in-sdkfor those Swift core modules.Can this pull be broadened to fix that too, especially since @compnerd has proposed looking in
-sdkprimarily for those Swift core modules?Right now, the way it works is that
swift-driverqueriesswift-frontendfor what paths to use then uses those to set-sdkand-resource-dirflags to pass back to theswift-frontendfor compiling new Swift files. During compilation,swift-frontendonly checks-resource-dirand adjacent to the compiler for the Swift core modules like the stdlib.I think we should change
swift-frontendto look in-sdkand adjacent to the compiler instead and stop passing-resource-dirto theswift-frontendunless one was specified toswift-driver. I noted in the linked issue that the legacy C++ Driver worked that way, ie it did not pass-resource-dirto theswift-frontendunless one was passed to the Driver first.This would be in keeping with Saleem's plan to de-emphasize
-resource-dirto look for Swift core modules and look in-sdkinstead.