6492c8576e
In other words, only executable files go in the MacOS folder. Dynamic libraries and bundled frameworks (i.e., LibreOfficePython), and nothing else, go in the Frameworks folder, and all other files go in the Resources folder. Especially, note that Java class files and rc (.ini) files also go in Resources. Such an app bundle structure is what Apple strongly suggests one should use, and it has been hinted that future versions of code signing and/or Gatekeeper will require such a structure. There is still some ugliness thanks to traces of the historical separation of URE from "the office". Like there are two separate "unorc" files, one for URE, one for the LibreOffice application. IMHO, this should be cleaned up, but is probably controversial. (Eek! I now see there are actually *three* unorc files in the app bundle. Not intentional. Need to fix that later.) Change-Id: Idcf235038deb5b8e1d061734993e9f31869b7606 |
||
|---|---|---|
| .. | ||
| demo | ||
| doc | ||
| inc/pyuno | ||
| qa/pytests | ||
| source | ||
| zipcore | ||
| CustomTarget_python_shell.mk | ||
| CustomTarget_zipcore.mk | ||
| Executable_python.mk | ||
| Library_pythonloader.mk | ||
| Library_pyuno.mk | ||
| Library_pyuno_wrapper.mk | ||
| Makefile | ||
| Module_pyuno.mk | ||
| Package_python_scripts.mk | ||
| Package_python_shell.mk | ||
| Package_zipcore.mk | ||
| PythonTest_pytests.mk | ||
| PythonTest_pyuno_pytests_insertremovecells.mk | ||
| PythonTest_pyuno_pytests_ssl.mk | ||
| Rdb_pyuno.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.