[all-commits] [llvm/llvm-project] 2121b9: [libc++abi][libunwind] Run c++abi and unwind tests...

[Louis Dionne via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 2121b961fd8f1cf5449a73a20643db53431e5bc0
      https://github.com/llvm/llvm-project/commit/2121b961fd8f1cf5449a73a20643db53431e5bc0
  Author: Louis Dionne <ldionne.2 at gmail.com>
  Date:   2024-09-30 (Mon, 30 Sep 2024)

  Changed paths:
    M libcxx/test/configs/llvm-libc++-shared-mingw.cfg.in
    M libcxx/test/configs/llvm-libc++-static-mingw.cfg.in
    M libcxxabi/src/CMakeLists.txt
    M libcxxabi/test/CMakeLists.txt
    M libcxxabi/test/configs/cmake-bridge.cfg.in
    M libcxxabi/test/configs/llvm-libc++abi-mingw.cfg.in
    M libunwind/CMakeLists.txt
    M libunwind/test/CMakeLists.txt
    M libunwind/test/configs/cmake-bridge.cfg.in
    R libunwind/test/configs/llvm-libunwind-mingw.cfg.in
    A libunwind/test/configs/llvm-libunwind-shared-mingw.cfg.in
    A libunwind/test/configs/llvm-libunwind-static-mingw.cfg.in

  Log Message:
  -----------
  [libc++abi][libunwind] Run c++abi and unwind tests against a fake install root (#110171)

This is what we started doing in libc++ and it straightens up a lot of
things that only happened to work before, notably the presence of
relative rpaths in dylibs when running from the build tree.

This unlocks the ability to link against a just-built dylib but run
against another version of the dylib (for example the system-provided
one), which is necessary for proper backdeployment testing.

This patch adds a lot of code duplication between the libc++ and
libc++abi testing setups. However, there is already a large amount of
duplication and the only real way to get rid of it is to merge libc++abi
into libc++. In a way, this patch is a step in that direction because it
closes the gap between the two libraries' testing setup.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications