Do not store Swift object files in subdirectories #6674
Merged
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
Looks like we have been using the full relative path from the target directory as basis for object file paths until now which seems odd and might also cause clashes with other files in the build directory. We should be using the basename here since duplicated basenames in the same Swift module are anyway prohibited. resolves #6672
|
@swift-ci please smoke test |
tomerd
approved these changes
Jul 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Looks like we have been using the full relative path from the target directory as basis for object file paths until now which seems odd and might also cause clashes with other files in the build directory. We should be using the basename here since duplicated basenames in the same Swift module are anyway prohibited.
resolves #6672