summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEd Maste <emaste@freebsd.org>2015-05-28 17:25:34 +0000
committerEd Maste <emaste@freebsd.org>2015-05-28 17:25:34 +0000
commit5f5b1e99aa09b020ff3929207ba3c88aed2d755a (patch)
tree1a47293b812e8f8a79beb183f8594a2e9903d27e
parent1c614fedf95a04f3d75c7562e96d21b5d732d6b1 (diff)
downloadbcm5719-llvm-5f5b1e99aa09b020ff3929207ba3c88aed2d755a.tar.gz
bcm5719-llvm-5f5b1e99aa09b020ff3929207ba3c88aed2d755a.zip
Add explicit dependency on headers to swig wrapper (cmake build)
This should avoid issues like that described in llvm.org/pr23686 Differential Revision: http://reviews.llvm.org/D10092 llvm-svn: 238441
-rw-r--r--lldb/scripts/CMakeLists.txt9
1 files changed, 9 insertions, 0 deletions
diff --git a/lldb/scripts/CMakeLists.txt b/lldb/scripts/CMakeLists.txt
index 9cfe6b9ba4a..e3503ddc635 100644
--- a/lldb/scripts/CMakeLists.txt
+++ b/lldb/scripts/CMakeLists.txt
@@ -2,6 +2,14 @@ set(LLVM_NO_RTTI 1)
file(GLOB SWIG_INTERFACES interface/*.i)
file(GLOB_RECURSE SWIG_SOURCES *.swig)
+set(SWIG_HEADERS
+ ${LLDB_SOURCE_DIR}/include/lldb/API/SBDefines.h
+ ${LLDB_SOURCE_DIR}/include/lldb/lldb-defines.h
+ ${LLDB_SOURCE_DIR}/include/lldb/lldb-enumerations.h
+ ${LLDB_SOURCE_DIR}/include/lldb/lldb-forward.h
+ ${LLDB_SOURCE_DIR}/include/lldb/lldb-types.h
+ ${LLDB_SOURCE_DIR}/include/lldb/lldb-versioning.h
+)
if ( LLDB_ENABLE_PYTHON_SCRIPTS_SWIG_API_GENERATION )
find_package(SWIG REQUIRED)
@@ -9,6 +17,7 @@ if ( LLDB_ENABLE_PYTHON_SCRIPTS_SWIG_API_GENERATION )
OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/LLDBWrapPython.cpp
DEPENDS ${SWIG_SOURCES}
DEPENDS ${SWIG_INTERFACES}
+ DEPENDS ${SWIG_HEADERS}
DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/buildSwigWrapperClasses.py
COMMAND ${PYTHON_EXECUTABLE} ${CMAKE_CURRENT_SOURCE_DIR}/buildSwigWrapperClasses.py "--srcRoot=${LLDB_SOURCE_DIR}" "--targetDir=${CMAKE_CURRENT_BINARY_DIR}" "--cfgBldDir=${CMAKE_CURRENT_BINARY_DIR}" "--prefix=${CMAKE_BINARY_DIR}" "--swigExecutable=${SWIG_EXECUTABLE}" -m
COMMENT "Python script building LLDB Python wrapper")
OpenPOWER on IntegriCloud