-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Do not add rpath to swift-testing for CLT or custom toolchains #8295
Conversation
@swift-ci please 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.
Oof, yes, adding this to the env makes sense. We'll have to keep an eye on this as we transition the build system to make sure it's doing what we need.
@swift-ci please test macOS platform |
This was added so that test binaries could find swift-testing, but we should insert those paths into `DYLD_*_PATH` rather than add to the rpath. The current behavior adds an absolute rpath to *all* binaries, not even just test binaries.
@swift-ci please test macOS platform |
@swift-ci please test Linux platform |
@swift-ci please test Windows platform |
@swift-ci please test Windows platform |
This was added so that test binaries could find swift-testing, but we should insert those paths into
DYLD_*_PATH
rather than add to the rpath. The current behavior adds an absolute rpath to all binaries, not even just test binaries.