summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/context-object/main.cpp
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2019-07-17 19:24:15 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2019-07-17 19:24:15 +0000
commitca12cb9482a23cd9596a1e55c94149994bf9909a (patch)
tree0fac64626e9ac15ac5678bed4c35038c18d965f6 /lldb/packages/Python/lldbsuite/test/expression_command/context-object/main.cpp
parent851339fb29527b483c2ca627d340ef9f4b074732 (diff)
downloadbcm5719-llvm-ca12cb9482a23cd9596a1e55c94149994bf9909a.tar.gz
bcm5719-llvm-ca12cb9482a23cd9596a1e55c94149994bf9909a.zip
[CMake] Use LLVM_DIR and Clang_DIR for standalone builds.
When doing a standalone build, without setting LLDB_PATH_TO_LLVM_BUILD or LLDB_PATH_TO_CLANG_BUILD, you get the following error. ``` CMake Error at cmake/modules/LLDBStandalone.cmake:23 (find_package): Could not find a package configuration file provided by "LLVM" with any of the following names: LLVMConfig.cmake llvm-config.cmake Add the installation prefix of "LLVM" to CMAKE_PREFIX_PATH or set "LLVM_DIR" to a directory containing one of the above files. If "LLVM" provides a separate development package or SDK, be sure it has been installed. ``` This suggests setting LLVM_DIR to LLVM's install directory. However, LLDBStandalone.cmake takes LLDB_PATH_TO_LLVM_BUILD as its hint. As someone who isn't familiar with the standalone process, this is rather confusing. This patch removes LLDB_PATH_TO_LLVM_BUILD and LLDB_PATH_TO_CLANG_BUILD and instead use LLVM_DIR and Clang_DIR respectively. Differential revision: https://reviews.llvm.org/D64823 llvm-svn: 366362
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/context-object/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud