aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2018-07-04 14:34:32 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2018-07-04 14:34:32 +0000
commitcfc2377333754cc4a1b63015bb4c92be767449ad (patch)
tree013a8c76c339b3657efcb441de1a7f0a975a7689
parent0c3b421b1aaad2c56feb203e52573125e5f218c4 (diff)
downloadllvm-cfc2377333754cc4a1b63015bb4c92be767449ad.zip
llvm-cfc2377333754cc4a1b63015bb4c92be767449ad.tar.gz
llvm-cfc2377333754cc4a1b63015bb4c92be767449ad.tar.bz2
[CMake] Use LLVM_RUNTIME_OUTPUT_INTDIR for LLDB exectuable
Apparently there's a difference between using LLVM_RUNTIME_OUTPUT_INTDIR and LLVM_BINARY_DIR. The former will point to the current binary directory (i.e. that where lldb is built) while the former will always point to LLVM's. This was causing trouble for the swift build but should be a transparent for upstream lldb. llvm-svn: 336278
-rw-r--r--lldb/CMakeLists.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/lldb/CMakeLists.txt b/lldb/CMakeLists.txt
index 1d67a73..2b08284 100644
--- a/lldb/CMakeLists.txt
+++ b/lldb/CMakeLists.txt
@@ -89,7 +89,10 @@ option(LLDB_TEST_USE_CUSTOM_C_COMPILER "Use the C compiler provided via LLDB_TES
option(LLDB_TEST_USE_CUSTOM_CXX_COMPILER "Use the C++ compiler provided via LLDB_TEST_CXX_COMPILER for building test inferiors (instead of the just-built compiler). Defaults to OFF." OFF)
if(LLDB_INCLUDE_TESTS)
- set(LLDB_DEFAULT_TEST_EXECUTABLE "${LLVM_BINARY_DIR}/${CMAKE_CFG_INTDIR}/bin/lldb${CMAKE_EXECUTABLE_SUFFIX}")
+ # The difference between the following two paths is significant. The path to
+ # LLDB will point to LLDB's binary directory, while the other will point to
+ # LLVM's binary directory in case the two differ.
+ set(LLDB_DEFAULT_TEST_EXECUTABLE "${LLVM_RUNTIME_OUTPUT_INTDIR}/bin/lldb${CMAKE_EXECUTABLE_SUFFIX}")
set(LLDB_DEFAULT_TEST_DSYMUTIL "${LLVM_BINARY_DIR}/${CMAKE_CFG_INTDIR}/bin/dsymutil${CMAKE_EXECUTABLE_SUFFIX}")
if (NOT LLDB_TEST_USE_CUSTOM_C_COMPILER AND TARGET clang)