summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/swig_bot_lib/client.py
Commit message (Collapse)AuthorAgeFilesLines
* [lldb/Scripts] Remove SWIG botJonas Devlieghere2020-01-131-216/+0
| | | | | | This is no longer used or maintained. Differential revision: https://reviews.llvm.org/D72539
* *** This commit represents a complete reformatting of the LLDB source codeKate Stone2016-09-061-8/+19
| | | | | | | | | | | | | | | | | | | | | | | *** 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
* Use sub-commands instead of --mode={client,server}.Zachary Turner2015-12-021-11/+3
| | | | | | | This is more pythonic and allows a more idiomatic way of getting detailed usage information for each individual sub-command. llvm-svn: 254533
* Unpack the output on the client, completing the cycle.Zachary Turner2015-11-301-4/+32
| | | | llvm-svn: 254341
* Have swig_bot actually run swig, and send back the output.Zachary Turner2015-11-301-10/+22
| | | | llvm-svn: 254340
* swig-bot - Close the socket when shutting down.Zachary Turner2015-11-241-5/+10
| | | | llvm-svn: 254026
* Include config settings in the archive, and extract on the remote.Zachary Turner2015-11-241-2/+9
| | | | llvm-svn: 254025
* swig_bot remote path connection / preliminary implementation.Zachary Turner2015-11-241-20/+73
| | | | | | | | | | | | | | | With this patch, the client will package up all the required inputs into a compressed zip file, establish a connection to the server, send the input to the server, and wait for the server to send a response (in this case the response is just echoed back to the client). This gets the network communication in place, and in a subsequent patch I will follow up with the code that actually runs swig on the server and sends back the output instead of echoing back the input. llvm-svn: 254023
* First implementation of swig_bot.pyZachary Turner2015-11-241-0/+108
This version supports local generation only. It's intentionally stupid, and does not support any kind of dependency checking. If you run the script, it's going to call SWIG. While this is a slow process, we are going to combine the use of the swig bot with checked in static bindings, meaning that it won't be terribly important to only regenerate the bindings when the input files have actually changed. A side benefit of this is that the implementation is drastically simpler. This is all experimental at the moment, but it duplicates a lot of the logic currently found in prepare_bindings.py. There was not a good way to reuse some of the logic without invasive changes on that script, and since this script is still experimental, it makes sense to just copy them over, and if / when this becomes more mature, we can get rid of the other ones. llvm-svn: 254022
OpenPOWER on IntegriCloud