forked from OSchip/llvm-project
11bc3f49da
Summary: Swig is perfectly capable of inserting blocks of python code into its output (and we use those fascilities already), so there's no need for this to be done in a post-process step. lldb_iter is a general-purpose utility used from many classes, so I add it to the main swig file. The other two blocks are tied to a specific class, so I add it to the interface file of that class. Reviewers: zturner, jingham, serge-sans-paille Subscribers: jdoerfert, lldb-commits Differential Revision: https://reviews.llvm.org/D58350 llvm-svn: 354975 |
||
---|---|---|
.. | ||
Python | ||
Xcode | ||
interface | ||
swig_bot_lib | ||
CMakeLists.txt | ||
analyze-project-deps.py | ||
build-lldb-llvm-clang | ||
buildbot.py | ||
checkpoint-llvm.pl | ||
disasm-gdb-remote.pl | ||
finish-swig-wrapper-classes.sh | ||
finishSwigWrapperClasses.py | ||
framework-header-fix.sh | ||
generate-vers.pl | ||
get_relative_lib_dir.py | ||
install-lldb.sh | ||
install_custom_python.py | ||
lldb.swig | ||
macos-setup-codesign.sh | ||
prepare_bindings.py | ||
sed-sources | ||
shush | ||
sort-pbxproj.rb | ||
swig_bot.py | ||
use_lldb_suite.py | ||
utilsArgsParse.py | ||
utilsDebug.py | ||
utilsOsType.py | ||
verify_api.py |