Skip to content
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

[BuildSystem] Move Swift compiler's aux files next to the object file #356

Merged
merged 1 commit into from Aug 1, 2018

Conversation

ankitspd
Copy link
Member

This is important for performing correct builds when there are two source files
with the same name in a Swift target.

rdar://problem/41060279 Nest all swift auxiliary files similar to the object files

This is important for performing correct builds when there are two source files
with the same name in a Swift target.

<rdar://problem/41060279> Nest all swift auxiliary files similar to the object files
@ankitspd
Copy link
Member Author

@swift-ci smoke test

Copy link
Contributor

@jrose-apple jrose-apple left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable, but may be worth adding a test case that would actually fail without this, so that we can catch problems the next time we add a supplementary output.

@ankitspd
Copy link
Member Author

Not sure if we can create a future proof test as the "failure" depends on the type of supplementary file.

@jrose-apple
Copy link
Contributor

I guess it would be hardcoding knowledge of the file map format, but you could check that no paths are duplicated throughout the file. (Honestly, the compiler could probably check that too, so maybe you should just file a JIRA bug and leave it at that.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants