-
Notifications
You must be signed in to change notification settings - Fork 206
Pass -use-static-resource-dir to frontend when linking statically #192
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
Conversation
@swift-ci test |
233028b
to
f7efa44
Compare
@swift-ci test |
f7efa44
to
610991d
Compare
@swift-ci test |
@swift-ci test macos |
610991d
to
d201490
Compare
@swift-ci test |
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 looks correct, although I think we also want to pass this down to -print-target-info
? With your fixes to the Swift compiler, we might be able to replace this driver's resource-dir computation with using the result of -print-target-info
, which would be wonderful.
Yes, good point. I‘ll add it to the target info. |
d201490
to
1f1ed5f
Compare
@swift-ci test |
bf16f7f
to
a2b269d
Compare
@swift-ci test |
a2b269d
to
311ddd5
Compare
@swift-ci test |
1 similar comment
@swift-ci test |
@swift-ci test macOS |
1 similar comment
@swift-ci test macOS |
@swift-ci test |
1 similar comment
@swift-ci test |
The compiler computes the resource folder based on its own executable path when it is not explicitly set, but it used to always pick the shared resource folder, because it did not have information about whether the binary will be statically or dynamically linked. This has been changed in swiftlang/swift#33168 and this PR adjusts the behavior to match that of the C++ implementation.