Skip to content

[cherry-pick][release/5.9] [Build] Make sure lldb API tests run against newly built libcxx #66026

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

Michael137
Copy link
Contributor

Currently any buildbot that runs LLDB API tests does so against the system SDK. However, we explicitly need users to run the tests against a newly built libcxx. We recently added a new LLDB_TEST_LIBCXX_ROOT_DIR CMake variable to LLDB to allow standalone builds to point their tests to a custom libcxx directory.

This patch makes sure the relevant LLDB presets build libcxx and then sets above CMake variable.

(cherry picked from commit 0c974e0)

Currently any buildbot that runs LLDB API tests does so
against the system SDK. However, we explicitly need users
to run the tests against a newly built libcxx. We recently
added a new `LLDB_TEST_LIBCXX_ROOT_DIR` CMake variable to
LLDB to allow standalone builds to point their tests to
a custom libcxx directory.

This patch makes sure the relevant LLDB presets build
libcxx and then sets above CMake variable.

(cherry picked from commit 0c974e0)
@Michael137
Copy link
Contributor Author

@swift-ci test

@adrian-prantl adrian-prantl merged commit 0f1eee5 into swiftlang:release/5.9 May 22, 2023
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