forked from amazingfate/loongoffice
9ac98e6e34
There is lots of (Windows-only) code that relied on sal_Unicode being the same as wchar_t, and the best change may be different in each case (and doing the changes may be somewhat error prone). So for now add SAL_U/SAL_W scaffolding functions to sal/types.h, remove their uses one by one again, and finally drop those functions again. Change-Id: I2cc791bd941d089901abb5f6fc2f05fbc49e65ea Reviewed-on: https://gerrit.libreoffice.org/36077 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
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. 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.