summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/Python/prepare_binding_Python.py
Commit message (Collapse)AuthorAgeFilesLines
* *** This commit represents a complete reformatting of the LLDB source codeKate Stone2016-09-061-1/+3
| | | | | | | | | | | | | | | | | | | | | | | *** to conform to clang-format’s LLVM style. This kind of mass change has *** two obvious implications: Firstly, merging this particular commit into a downstream fork may be a huge effort. Alternatively, it may be worth merging all changes up to this commit, performing the same reformatting operation locally, and then discarding the merge for this particular commit. The commands used to accomplish this reformatting were as follows (with current working directory as the root of the repository): find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} + find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ; The version of clang-format used was 3.9.0, and autopep8 was 1.2.4. Secondly, “blame” style tools will generally point to this commit instead of a meaningful prior commit. There are alternatives available that will attempt to look through this change and find the appropriate prior commit. YMMV. llvm-svn: 280751
* Fix SBDebugger.GetOutputFileHandle() on OS X.Jim Ingham2016-03-111-1/+3
| | | | | | | | | | | | | | | | | | | | | | | The swig typemaps had some magic for output File *'s on OS X that made: SBDebugger.GetOutputFileHandle() actually work. That was protected by a "#ifdef __MACOSX__", but the corresponding define got lost going from the Darwin shell scripts to the python scripts for running swig, so the code was elided. I need to pass the define to SWIG, but only when targetting Darwin. So I added a target-platform argument to prepare_bindings, and if that is Darwin, I pass -D__APPLE__ to swig, and that activates this code again, and GetOutputFileHandle works again. Note, I only pass that argument for the Xcode build. I'm sure it is possible to do that for cmake, but my cmake-foo is weak. I should have been able to write a test for this by creating a debugger, setting the output file handle to something file, writing to it, getting the output file handle and reading it. But SetOutputFileHandle doesn't seem to work from Python, so I'd have to write a pexpect test to test this, which I'd rather not do. llvm-svn: 263183
* Revert "prepare_bindings.py: enable static bindings"Todd Fiala2015-11-191-50/+7
| | | | | | This reverts commit 40f789f2dc6bb80fd25a33f91e452d081ed9d0ee. llvm-svn: 253575
* prepare_bindings.py: enable static bindingsTodd Fiala2015-11-181-7/+50
| | | | | | | | | | | | | | | Added a new flag, --allow-static-binding. When specified, if (and only if) the swig binary cannot be found, then the LLDBWrapPython.cpp and lldb.py from the scripts/Python/{static-binding-dir} are copied into the place where swig would have generated them. {static-binding-dir} defaults to static-binding, and can be overridden with the --static-binding-dir command line argument. The static bindings checked in are from r253424. llvm-svn: 253448
* Add Pythonic language binding wrapper generation script.Todd Fiala2015-11-171-0/+435
This is only used by Xcode at the moment. It replaces the buildSwigWrapperClasses.py and related per-script-language scripts. It also fixes a couple bugs in those w/r/t Xcode usage: * the presence of the GCC_PREPROCESSOR_DEFINITIONS env var should not be short-circuiting generation of the language binding; rather, only if LLDB_DISABLE_PYTHON is present within that environment variable. * some logic around what to do when building in "non-Makefile" mode. I've switched the handling of that to be on a "--framework" flag - if specified, we build an OS X-style framework; otherwise, we go with non. Putting this up now only attached to the Xcode build so others can look at it but not be affected by it yet. After this, I'll tackle the finalizer, along with trying it locally on Linux. llvm-svn: 253317
OpenPOWER on IntegriCloud