ed26c01be1
ExternalProject usually involve a configure and a make step that produce a bunch of output usually irrelevant including a large number of warning and other mess. now that everything is pretty much in tail_build these output get interleaved with useful output from the build of the product and actually drown them in a logorrhea of messy noise. This store the output of external modules in a log file and only print them as a whole if the module failed do build. on a non-verbose build. Change-Id: I3abfcccd6d16821a9e061a71e031b427cc283647 Reviewed-on: https://gerrit.libreoffice.org/2304 Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com> Tested-by: Norbert Thiebaud <nthiebaud@gmail.com> |
||
|---|---|---|
| .. | ||
| demo | ||
| doc | ||
| inc/pyuno | ||
| prj | ||
| source | ||
| zipcore | ||
| CustomTarget_python_bin.mk | ||
| CustomTarget_python_shell.mk | ||
| CustomTarget_zipcore.mk | ||
| Executable_python_wrapper.mk | ||
| Library_pythonloader.mk | ||
| Library_pyuno.mk | ||
| Library_pyuno_wrapper.mk | ||
| Makefile | ||
| Module_pyuno.mk | ||
| Package_python_bin.mk | ||
| Package_python_scripts.mk | ||
| Package_python_shell.mk | ||
| Package_pyunorc.mk | ||
| Package_zipcore.mk | ||
| README | ||
UNO bindings for the Python programming language. To have much joy debugging python extensions you need to: a) edit pythonloader.py in your install setting DEBUG=1 at the top b) touch pyuno/source/module/pyuno_runtime.cxx and 'make debug=true' in pyuno Then you'll start to see your exceptions on the console instead of them getting lost at the UNO interface.