diff options
| author | Vlad Serebrennikov <serebrennikov.vladislav@gmail.com> | 2025-03-25 19:38:33 +0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-25 19:38:33 +0400 |
| commit | 8f863fcd77e15caf3b7fde089adc223b0c4fb103 (patch) | |
| tree | 975f84cd236187866f1ff18f8d376ba09fcebe7f /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp | |
| parent | feecb201ab041dbcf8266960aba4b252a789bcd4 (diff) | |
[clang][CI] Reuse build dir between C++26 and modules build of runtimes (#132480)
Between C++26 and Clang modules build of runtimes, which are used as an
additional testing for Clang, the only difference are
`LIBCXX_TEST_PARAMS` and `LIBCXXABI_TEST_PARAMS`. Both of them are
transformed into actual lit configuration lines, and put into
`SERIALIZED_LIT_PARAMS`, which end up in `libcxx/test/cmake-bridge.cfg`
via `configure_file` command. Notably, it seems that they are not used
in any other way.
I checked that if those variables are changed, subsequent runs of CMake
configuration step regenerate `cmake-bridge.cfg` with the new values.
Which means that we don't need to do clean builds for every runtimes
configuration we want to test.
I hope that together with #131913, this will be enough to alleviate
Linux CI pains we're having, and we wouldn't have to make a tough choice
between C++26 and Clang modules builds for pre-merge CI.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp')
0 files changed, 0 insertions, 0 deletions
