Neil Roberts
c1f4dc187b
On macOS a hard-coded path is used for the soffice binary. It probably makes sense to avoid doing this if the UNO_PATH environment variable is set. Change-Id: I160bbec8a7ddffbb7032b55a61a3004e9d42bf18 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/206263 Tested-by: Jenkins Reviewed-by: Neil Roberts <nroberts@libreoffice.org>
Python UNO Bindings
UNO bindings for the Python programming language.
To have much joy debugging Python extensions you need to:
- a) edit
pythonloader.pyin your install settingDEBUG=1at the top - b)
touch pyuno/source/module/pyuno_runtime.cxxandmake debug=trueinpyuno
Then you'll start to see your exceptions on the console instead of them getting lost at the UNO interface.
Python also comes with a gdb script
libpython$(PYTHON_VERSION_MAJOR).$(PYTHON_VERSION_MINOR)m.so.1.0-gdb.py
that is copied to instdir and will be auto-loaded by gdb;
it provides commands like py-bt to get a Python-level backtrace,
and py-print to print Python variables.
Another way to debug Python code is to use pdb: edit some initialization
function to insert import pdb; pdb.set_trace() (somewhere so that it is
executed early), then run soffice from a terminal and a command-line Python
debugger will appear where you can set Python-level breakpoints.