diff options
| author | Jonas Devlieghere <jonas@devlieghere.com> | 2019-07-17 19:36:20 +0000 |
|---|---|---|
| committer | Jonas Devlieghere <jonas@devlieghere.com> | 2019-07-17 19:36:20 +0000 |
| commit | e37750b93440de1d4b42cb731b0f20c981e6f74d (patch) | |
| tree | f8620ae669950bcf7ff7612da55039f01f3cb328 /lldb | |
| parent | ca12cb9482a23cd9596a1e55c94149994bf9909a (diff) | |
| download | bcm5719-llvm-e37750b93440de1d4b42cb731b0f20c981e6f74d.tar.gz bcm5719-llvm-e37750b93440de1d4b42cb731b0f20c981e6f74d.zip | |
[CMake] Remove duplicated logic to find Python when doing a standalone build
I'm pretty sure there's no need to have this logic living in
LLDBStandalone. It doesn't appear anything in LLVM depends on this, and
We always go through LLDBConfig.cmake which has the canonical way to
find the Python libs and interpreter for LLDB.
Differential revision: https://reviews.llvm.org/D64821
llvm-svn: 366363
Diffstat (limited to 'lldb')
| -rw-r--r-- | lldb/cmake/modules/LLDBStandalone.cmake | 12 |
1 files changed, 0 insertions, 12 deletions
diff --git a/lldb/cmake/modules/LLDBStandalone.cmake b/lldb/cmake/modules/LLDBStandalone.cmake index 8d89f7c2943..b726797f876 100644 --- a/lldb/cmake/modules/LLDBStandalone.cmake +++ b/lldb/cmake/modules/LLDBStandalone.cmake @@ -77,18 +77,6 @@ include(HandleLLVMOptions) include(CheckAtomic) include(LLVMDistributionSupport) -set(Python_ADDITIONAL_VERSIONS 3.7 3.6 3.5 2.7) -if (PYTHON_EXECUTABLE STREQUAL "") - include(FindPythonInterp) - if( NOT PYTHONINTERP_FOUND ) - message(FATAL_ERROR - "Unable to find Python interpreter, required for builds and testing. - Please install Python or specify the PYTHON_EXECUTABLE CMake variable.") - endif() -else() - message(STATUS "Found PythonInterp: ${PYTHON_EXECUTABLE}") -endif() - set(PACKAGE_VERSION "${LLVM_PACKAGE_VERSION}") set(LLVM_INCLUDE_TESTS ON CACHE INTERNAL "") |
