summaryrefslogtreecommitdiff
path: root/lib/Driver/ToolChains/Fuchsia.cpp
diff options
context:
space:
mode:
authorPetr Hosek <phosek@chromium.org>2019-03-08 05:35:22 +0000
committerPetr Hosek <phosek@chromium.org>2019-03-08 05:35:22 +0000
commit60510251f0c7e121e59a5477103c53e69833ca56 (patch)
treed463fa89f066c3e8f84d16e9690862dce2b90850 /lib/Driver/ToolChains/Fuchsia.cpp
parentae78f33054b081980625557c31599d3548954461 (diff)
downloadclang-60510251f0c7e121e59a5477103c53e69833ca56.tar.gz
[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 git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@355665 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/Driver/ToolChains/Fuchsia.cpp')
-rw-r--r--lib/Driver/ToolChains/Fuchsia.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/Driver/ToolChains/Fuchsia.cpp b/lib/Driver/ToolChains/Fuchsia.cpp
index 0db6d0e159..a31544b551 100644
--- a/lib/Driver/ToolChains/Fuchsia.cpp
+++ b/lib/Driver/ToolChains/Fuchsia.cpp
@@ -257,8 +257,8 @@ void Fuchsia::AddClangCXXStdlibIncludeArgs(const ArgList &DriverArgs,
switch (GetCXXStdlibType(DriverArgs)) {
case ToolChain::CST_Libcxx: {
- SmallString<128> P(getDriver().ResourceDir);
- llvm::sys::path::append(P, "include", "c++", "v1");
+ SmallString<128> P(getDriver().Dir);
+ llvm::sys::path::append(P, "..", "include", "c++", "v1");
addSystemInclude(DriverArgs, CC1Args, P.str());
break;
}