Skip to content

[CMake] Use explicit RPATHs for unit test executables #68388

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 1 commit into from
Sep 8, 2023

Conversation

rintaro
Copy link
Member

@rintaro rintaro commented Sep 7, 2023

Instead of letting CMake set RPATH of the test executables, use INSTALL_RPATH and BUILD_WITH_INSTALL_RPATH just like other executable and shared libraries.

Previously when a swift module link with exported swift-syntax targets e.g. 'SwiftSyntax::SwiftParser', the libraries in earlyswiftsyntax were used instead of the copied libraries in the swift build directory. That wasn't ideal.

@rintaro
Copy link
Member Author

rintaro commented Sep 7, 2023

@swift-ci Please smoke test

@rintaro rintaro requested a review from bnbarham September 8, 2023 00:14
@rintaro rintaro force-pushed the cmake-unittest-rpath branch from 341daea to e544164 Compare September 8, 2023 16:41
@rintaro
Copy link
Member Author

rintaro commented Sep 8, 2023

@swift-ci Please smoke test

Instead of letting CMake set RPATH of the test executables, use
INSTALL_RPATH and BUILD_WITH_INSTALL_RPATH just like other executable
and shared libraries.

Previously when a swift module link with exported swift-syntax targets e.g.
'SwiftSyntax::SwiftParser', the libraries in earlyswiftsyntax were used
instead of the copied libraries in the swift build directory. That
wasn't ideal.
@rintaro rintaro force-pushed the cmake-unittest-rpath branch from e544164 to 891d7b7 Compare September 8, 2023 16:43
@rintaro
Copy link
Member Author

rintaro commented Sep 8, 2023

@swift-ci Please smoke test

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.

2 participants