Closed pisajew closed 3 years ago
My build environment (and the environment used in CI to generate new releases) is Catalina; I haven't tried using Big Sur. I'm guessing the issues you've found relate to that version bump - we've seen analogous failures in the past. The problem is caused because Apple introduces or deprecates an API that autoconf didn't previously pick up. We'll need to update the patches to accomodate those changes.
Beyond that, the workflow should be nothing more than "make iOS". If you've got homebrew installed and you have gettext installed in that environment, you can get some problems at runtime. There's also a known problem with the webbrowser module at runtime with Python 3.7+; addressing this is on my todo list. Other than those problems, the build should be straightforward - and the Github Actions CI configuration on this repository has been used to produce the most recently published support packages.
Thanks. It was the gettext issue, as you described. Uninstalling it via homebrew fixes the issue for me. As a side effect I can confirm that dev builds on BigSur. It seems however that it needs the HAVE_SENDFILE undef patch.
Hi,
I wonder if you could provide some details on required build environment to build an embeddable Python for iOS from source.
My current build environment is:
I start by checking out the
dev
branch and try to build usingmake clean iOS
This fails at some point with error:
To fix this I've changed Makefile to set
MACOSX_DEPLOYMENT_TARGET
to 11 instead of 10.8.Then attempts to build fail with:
To resolve this I apply this patch:
this moves the compilation process a bit further, but eventually fails with:
Would it be possible for you to provide some recommendation on the build environment and flow to succesfully build a package for Python 3.8?