[libc++][tests] Use CMake provided paths for includes and libdir instead of hardcodin...
authorLouis Dionne <ldionne.2@gmail.com>
Tue, 15 Mar 2022 14:49:49 +0000 (10:49 -0400)
committerLouis Dionne <ldionne.2@gmail.com>
Wed, 16 Mar 2022 16:35:06 +0000 (12:35 -0400)
commit78669c4185e4f8784308b5e740721cd374052cae
tree88aeee8df5b0a19d1fa686a052d74f802f8c075e
parenta36d269658dfd8b16dd8bdcb1726b9206b1d97ff
[libc++][tests] Use CMake provided paths for includes and libdir instead of hardcoding them

In the new-style testing configurations, we were hardcoding paths to the
`include` and `lib` directories, which was incorrect but always went
unnoticed because the hardcoded values always happened to match the
actual value.

When using new-style configs with the bootstrapping build, this falls
appart -- and we never noticed this because the bootstrapping build was
still using old style configs.

This patch removes the %{install} substitution, which makes it too
tempting to hardcode installation paths, and it also switches the
bootstrapping build to actually using new-style configs like we
always intended to do.

Differential Revision: https://reviews.llvm.org/D121700
12 files changed:
libcxx/test/configs/apple-libc++-backdeployment.cfg.in
libcxx/test/configs/apple-libc++-shared.cfg.in
libcxx/test/configs/cmake-bridge.cfg.in
libcxx/test/configs/ibm-libc++-shared.cfg.in
libcxx/test/libcxx/vendor/apple/system-install-properties.sh.cpp
libcxx/utils/ci/run-buildbot
libcxx/utils/libcxx/test/config.py
libcxxabi/test/configs/apple-libc++abi-backdeployment.cfg.in
libcxxabi/test/configs/apple-libc++abi-shared.cfg.in
libcxxabi/test/configs/cmake-bridge.cfg.in
libcxxabi/test/configs/ibm-libc++abi-shared.cfg.in
libcxxabi/test/vendor/apple/system-install-properties.sh.cpp