[WIP] Fix configure for python's recipes when building from macOS#1682
[WIP] Fix configure for python's recipes when building from macOS#1682opacam wants to merge 1 commit intokivy:developfrom
configure for python's recipes when building from macOS#1682Conversation
This should solve the linkage problems with libpythonX.X.so that we have when we Build from a darwin platform Note: The added patches are migrated from the python2legacy recipe to match the new python version
|
Thanks @opacam, this is great to have to point people at. |
|
I am busy testing the solution now. The error which I am receiving is the same as before and after applying the solution. Although I must admit that I am very new to c++ and .mk syntax OS=Mojave --------------------CONSOLE DUMP-------------- Some warnings and things. STDOUT: |
It turns out that the generated binary for MacOS is not `python`...its `python.exe` See also: https://github.com/python/cpython/blob/3.7/README.rst#build-instructions Closes: kivy#1817 Closes: kivy#1800 Closes: kivy#1682 Closes: kivy#1647
This is a long shot
This pr is made in order to try to solve the linkage problems that we have when using a macOS as a host system.
Here I migrate a macOS's patch from python2legacy's recipe that we need in order to successfully link when building from a macOS. I suspect that we still may need that for the new python recipes...so ...I think that this pr may solve the linkage problems that we currently have, described in here #1647.
Unfortunately I couldn't test this (I haven't a macOS to test it)...so...
this should not be merged unless we can confirm that actually solves the problem