Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2020-01-13T17:23:48+00:00 2020-01-13T17:23:48+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-13T17:23:48+00:00 urn:sha1:f2bbe8ede057af13b56949f24bbfb436f8a55f97 This is no longer used or maintained. Differential revision: https://reviews.llvm.org/D72539 2020-01-10T21:54:33+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-10T21:54:31+00:00 urn:sha1:7c47a3719a9e587fdf993637dc09d97b5397483b The scripts root directory already contains python scripts. No need to keep this one nested under a dedicated Python directory. 2020-01-10T21:53:12+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-10T21:53:10+00:00 urn:sha1:e6d219122d5a94fa8642c67c391aeb47fc032c89 With Xcode gone this is no longer relevant. 2020-01-10T21:44:41+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-10T21:44:00+00:00 urn:sha1:1a8c996a8894a6ae2bf3b98780972bc7bdb6b8e6 This file is outdated and still references SVN. Buildbots are configured through the zorg repository. 2020-01-09T16:44:34+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-09T15:57:59+00:00 urn:sha1:6498aff249a1c3c6bad33137df3b90e2973722d6 All the code required to generate the language bindings for Python and Lua lives under scripts, even though the majority of this code aren't scripts at all, and surrounded by scripts that are totally unrelated. I've reorganized these files and moved everything related to the language bindings into a new top-level directory named bindings. This makes the corresponding files self contained and much more discoverable. Differential revision: https://reviews.llvm.org/D72437 2020-01-09T16:15:41+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-09T16:13:25+00:00 urn:sha1:93a1e9c90c96a9130352bf358d7777f0379ebb48 Making the string conversion operator a macro unintentionally dropped the backslash before '\n' and '\r' and was therefore incorrectly stripping 'n' and 'r' from the object description. 2020-01-09T05:02:59+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-09T04:56:11+00:00 urn:sha1:51bdd98b8a52d07004bcaddff26caf376a1c32bf The current SWIG extensions for the string conversion operator is Python specific because it uses the PythonObjects. This means that the code cannot be reused for other SWIG supported languages such as Lua. This reimplements the extensions in a more generic way that can be reused. It uses a SWIG macro to reduce code duplication. Differential revision: https://reviews.llvm.org/D72377 2020-01-09T00:34:09+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-09T00:13:03+00:00 urn:sha1:ae47a3d8107856c84c104f3c2e43a553f4e36748 The current SWIG extensions for the string conversion operator is Python specific because it uses the PythonObjects. This means that the code cannot be reused for other SWIG supported languages such as Lua. This reimplements the extensions in a more generic way that can be reused. It uses a SWIG macro to reduce code duplication. Differential revision: https://reviews.llvm.org/D72377 2020-01-08T21:37:07+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-08T21:34:55+00:00 urn:sha1:0341c11e08504acef8c16ab07210bc253dadf2d9 The current SWIG extensions for the string conversion operator is Python specific because it uses the PythonObjects. This means that the code cannot be reused for other SWIG supported languages such as Lua. This reimplements the extensions in a more generic way that can be reused. Differential revision: https://reviews.llvm.org/D72377 2020-01-08T05:57:32+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-08T05:53:33+00:00 urn:sha1:fc6f15d4d2c4a051c8e31fe4de0bfaf9d3535f6e As correctly pointed out by Martin on the mailing list, Python should only be auto-enabled if SWIG is found as well. This moves the logic of finding SWIG into FindPythonInterpAndLibs to make that possible. To make diagnosing easier I've included a status message to convey why Python support is disabled.