[runtimes] Move libunwind, libc++abi and libc++ to lib/ and include/
authorPetr Hosek <phosek@chromium.org>
Fri, 8 Mar 2019 05:35:22 +0000 (05:35 +0000)
committerPetr Hosek <phosek@chromium.org>
Fri, 8 Mar 2019 05:35:22 +0000 (05:35 +0000)
commit28302c66d2586074f77497d5dc4eac7182b679e0
tree97f4f3a2694715600b503377dcc93cfbeea1fb12
parenta453455cee6767589638caca2f533184577ec745
[runtimes] Move libunwind, libc++abi and libc++ to lib/ and include/

This change is a consequence of the discussion in "RFC: Place libs in
Clang-dedicated directories", specifically the suggestion that
libunwind, libc++abi and libc++ shouldn't be using Clang resource
directory.  Tools like clangd make this assumption, but this is
currently not true for the LLVM_ENABLE_PER_TARGET_RUNTIME_DIR build.
This change addresses that by moving the output of these libraries to
lib/<target> and include/ directories, leaving resource directory only
for compiler-rt runtimes and Clang builtin headers.

Differential Revision: https://reviews.llvm.org/D59013

llvm-svn: 355665
clang/lib/Driver/ToolChain.cpp
clang/lib/Driver/ToolChains/Fuchsia.cpp
clang/lib/Driver/ToolChains/Linux.cpp
clang/test/Driver/linux-per-target-runtime-dir.c
libcxx/CMakeLists.txt
libcxx/lib/CMakeLists.txt
libcxxabi/CMakeLists.txt
libcxxabi/src/CMakeLists.txt
libunwind/CMakeLists.txt
libunwind/src/CMakeLists.txt
llvm/runtimes/CMakeLists.txt