[Explicit Module Builds] Handle dependency scanners that produce -o arguments explicitly
#1284
Conversation
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
… arguments explicitly - Only add '-o' when a swift interface dependency command does not already - Stop resolving module paths to a hashed output path because toolchains have had scanners that do this automatically for a while
Contributor
Author
|
@swift-ci test |
nkcsgexi
approved these changes
Feb 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
-owhen a swift interface dependency command does not alreadyThis is a half-measure which will help land the refactor in swiftlang/swift#63460.
The actual long-term driver solution will be landed in #1282.