Skip to content

Remove computeResourceDirPath and rely on the one reported by -print-target-info #354

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

Merged
merged 3 commits into from
Nov 11, 2020

Conversation

owenv
Copy link
Contributor

@owenv owenv commented Nov 9, 2020

In theory this is NFC, but I'll run full CI just in case (Edit: looks like it passed). In addition to replacing all uses of the old method with reference to the target info's runtimeResourcePath, I had to update the -print-target-info job in toolchain computation to ensure it returned the static resource directory when needed. I tried replacing all uses of runtime library paths with the -print-target-info version too but ran into some issues where the macosx paths weren't included for catalyst targets, I'll need to look into that more.

@owenv
Copy link
Contributor Author

owenv commented Nov 9, 2020

@swift-ci please test

@cltnschlosser
Copy link
Contributor

Does this fix something or is it just clean up?

@owenv
Copy link
Contributor Author

owenv commented Nov 9, 2020

@cltnschlosser it's just cleanup, this shouldn't change any observable behavior

@owenv owenv requested review from DougGregor and artemcm November 10, 2020 03:28
Copy link
Contributor

@artemcm artemcm left a comment

Choose a reason for hiding this comment

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

This looks like really good cleanup, thank you @owenv. 👍

@owenv
Copy link
Contributor Author

owenv commented Nov 11, 2020

@swift-ci please test

@owenv owenv merged commit 92bf1e4 into swiftlang:main Nov 11, 2020
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.

3 participants