Fix building Python3 on linux#490
Conversation
Apply the same logic as for the _md5 and _shaXXX modules.
Explicitly name the possible _sysconfigdata_XXX.py files. Copy the cpython include subdirectory.
|
Why don't we use the system Python on Linux? Do macros work with it? |
|
I suppose we are not using system-provided Python (and also other additional dependencies) due to the possible age difference between the distro of the build system and the distro of the actual systems on which AOO will run. |
|
main\pyuno\source\module\pyuno_dlopenwrapper.c Isnt that an issue? what we need is a dialog similar or same that lists as with java, so we can point python to a sandbox. |
I suppose not. The build system should take care of indicating the proper include file paths: either local to the AOO build tree, or at system level. |
|
I just built on openSUSE Leap 16.0, that ships Python 3.13.13. Macros are accessible when using system Python. |
I am afraid that using system level Python would make the AOO binary incompatible, or would raise compatibility issues, with other distributions having other system Python versions. |
These commits should allow to compile Python 3.11.15 on Linux.
However, after applying them, Python macros do not seem to work. But at least, we can get to compile trunk again.