summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/utilsArgsParse.py
Commit message (Collapse)AuthorAgeFilesLines
* [lldb] move package generation from python to cmakeHaibo Huang2019-10-281-141/+0
| | | | | | | | | | Summary: This is the last part. And we can remove the python script. Subscribers: lldb-commits, mgorny Tags: #lldb Differential Revision: https://reviews.llvm.org/D69019
* Install six.py conditionallyKamil Rytarowski2017-02-041-2/+2
| | | | | | | | | | | | | | | | | | | | | | | Summary: The current version of LLDB installs six.py into global python library directory. This approach produces conflicts downstream with distribution's py-six copy. Introduce new configure option LLDB_USE_SYSTEM_SIX (disabled by default). Once specified as TRUE, six.py won't be installed to Python's directory. Add new option in finishSwigWrapperClasses.py, namely --useSystemSix. Sponsored by <The NetBSD Foundation> Reviewers: mgorny, emaste, clayborg, joerg, labath Reviewed By: labath Subscribers: #lldb Tags: #lldb Differential Revision: https://reviews.llvm.org/D29405 llvm-svn: 294071
* *** This commit represents a complete reformatting of the LLDB source codeKate Stone2016-09-061-3/+5
| | | | | | | | | | | | | | | | | | | | | | | *** 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
* [swig] Start of pylint on python build scripts.Bruce Mitchener2015-11-051-125/+123
| | | | | | | | | | | | | | | | | | | | | | | Summary: This does a broad first pass on cleaning up a lot of the noise when using pylint on these scripts. It mostly addresses issues of: * Mixed tabs and spaces. * Trailing whitespace. * Semicolons where they aren't needed. * Incorrect whitespace around () and []. * Superfluous parentheses. There will be subsequent patches with further changes that build upon these. Reviewers: zturner, domipheus Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D14375 llvm-svn: 252244
* Run py2to3 on lldb/scripts folder.Zachary Turner2015-10-191-1/+1
| | | | | | | This mostly fixes some print statements, but there were also some instances of dict.iteritems() lingering that this found. llvm-svn: 250762
* Update swig generation scripts to support Python 3.Zachary Turner2015-10-061-1/+1
| | | | llvm-svn: 249467
* Remove non-standard Environment header sectionEd Maste2015-03-231-4/+0
| | | | llvm-svn: 232973
* Find SWIG with CMakeIsmail Pazarbasi2014-11-181-2/+1
| | | | | | | | | | SWIG is searched under certain paths within python script. CMake can detect SWIG with find_package(SWIG). This is used iff user checks LLDB_ENABLE_PYTHON_SCRIPTS_SWIG_API_GENERATION. If buildSwigWrapperClasses.py does not receive swigExecutable argument, then the script will use its current search implementation. llvm-svn: 222262
* This creates a valid Python API for Windows, pending some issues. The ↵Deepak Panickal2014-07-011-0/+146
changes included are - - Ported the SWIG wrapper shell scripts to Python so that they would work on Windows too along with other platforms - Updated CMake handling to fix SWIG errors and manage sym-linking on Windows to liblldb.dll - More build fixes for Windows The pending issues are that two Python modules, termios and pexpect are not available on Windows. These are currently required for the Python command interpreter to be used from within LLDB. llvm-svn: 212111
OpenPOWER on IntegriCloud