summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite
diff options
context:
space:
mode:
authorAlex Langford <apl@fb.com>2019-01-22 19:26:42 +0000
committerAlex Langford <apl@fb.com>2019-01-22 19:26:42 +0000
commitb8ecd7e49b83ecdcc2c3e86e1040a27cc499bb0c (patch)
treeb619cc86872466fe60d479650e6bd9b6187a998b /lldb/packages/Python/lldbsuite
parentb272ec13471bac281a3eaaafeb7d843469c2d103 (diff)
downloadbcm5719-llvm-b8ecd7e49b83ecdcc2c3e86e1040a27cc499bb0c.tar.gz
bcm5719-llvm-b8ecd7e49b83ecdcc2c3e86e1040a27cc499bb0c.zip
[CMake] Replace use of llvm-config with LLVM and Clang CMake packages
Summary: I did this for two reasons: - Using the CMake packages simplifies building LLDB Standalone. This is for two reasons: 1) We were doing a decent amount of work that is already done in the LLVMConfig.cmake that we want to import, 2) We had to do some manual work to call llvm-config, parse its output, and populate variables that the build system uses. - As far as I understand, using llvm-config makes it difficult if not impossible to cross-compile LLDB standalone. Reviewers: sgraenitz, labath, zturner, JDevlieghere, davide, aprantl, stella.stamenova Subscribers: mgorny, lldb-commits Differential Revision: https://reviews.llvm.org/D56531 llvm-svn: 351863
Diffstat (limited to 'lldb/packages/Python/lldbsuite')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud