gh-120831: Increase the default minimum supported iOS version to 13.0 (#121250)

Increases the default minimum iOS version to 13.0.

Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
This commit is contained in:
Russell Keith-Magee 2024-07-16 14:23:35 +10:00 committed by GitHub
parent 2bac2b86b1
commit 7e91e0dcfe
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
5 changed files with 23 additions and 5 deletions

View File

@ -33,6 +33,17 @@ running, so you only need to deal with the Python code itself.
Python at runtime on iOS
========================
iOS version compatibility
-------------------------
The minimum supported iOS version is specified at compile time, using the
:option:`--host` option to ``configure``. By default, when compiled for iOS,
Python will be compiled with a minimum supported iOS version of 13.0. To use a
different miniumum iOS version, provide the version number as part of the
:option:`!--host` argument - for example,
``--host=arm64-apple-ios15.4-simulator`` would compile an ARM64 simulator build
with a deployment target of 15.4.
Platform identification
-----------------------

View File

@ -0,0 +1 @@
The default minimum iOS version was increased to 13.0.

8
configure generated vendored
View File

@ -4108,7 +4108,7 @@ printf "%s\n" "\"$MACHDEP\"" >&6; }
# On cross-compile builds, configure will look for a host-specific compiler by
# prepending the user-provided host triple to the required binary name.
#
# On iOS, this results in binaries like "arm64-apple-ios12.0-simulator-gcc",
# On iOS, this results in binaries like "arm64-apple-ios13.0-simulator-gcc",
# which isn't a binary that exists, and isn't very convenient, as it contains the
# iOS version. As the default cross-compiler name won't exist, configure falls
# back to gcc, which *definitely* won't work. We're providing wrapper scripts for
@ -4523,8 +4523,12 @@ if test "$cross_compiling" = yes; then
_host_device=${_host_device:=os}
# IPHONEOS_DEPLOYMENT_TARGET is the minimum supported iOS version
{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking iOS deployment target" >&5
printf %s "checking iOS deployment target... " >&6; }
IPHONEOS_DEPLOYMENT_TARGET=${_host_os:3}
IPHONEOS_DEPLOYMENT_TARGET=${IPHONEOS_DEPLOYMENT_TARGET:=12.0}
IPHONEOS_DEPLOYMENT_TARGET=${IPHONEOS_DEPLOYMENT_TARGET:=13.0}
{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $IPHONEOS_DEPLOYMENT_TARGET" >&5
printf "%s\n" "$IPHONEOS_DEPLOYMENT_TARGET" >&6; }
case "$host_cpu" in
aarch64)

View File

@ -382,7 +382,7 @@ AC_MSG_RESULT(["$MACHDEP"])
# On cross-compile builds, configure will look for a host-specific compiler by
# prepending the user-provided host triple to the required binary name.
#
# On iOS, this results in binaries like "arm64-apple-ios12.0-simulator-gcc",
# On iOS, this results in binaries like "arm64-apple-ios13.0-simulator-gcc",
# which isn't a binary that exists, and isn't very convenient, as it contains the
# iOS version. As the default cross-compiler name won't exist, configure falls
# back to gcc, which *definitely* won't work. We're providing wrapper scripts for
@ -774,8 +774,10 @@ if test "$cross_compiling" = yes; then
_host_device=${_host_device:=os}
# IPHONEOS_DEPLOYMENT_TARGET is the minimum supported iOS version
AC_MSG_CHECKING([iOS deployment target])
IPHONEOS_DEPLOYMENT_TARGET=${_host_os:3}
IPHONEOS_DEPLOYMENT_TARGET=${IPHONEOS_DEPLOYMENT_TARGET:=12.0}
IPHONEOS_DEPLOYMENT_TARGET=${IPHONEOS_DEPLOYMENT_TARGET:=13.0}
AC_MSG_RESULT([$IPHONEOS_DEPLOYMENT_TARGET])
case "$host_cpu" in
aarch64)

View File

@ -188,7 +188,7 @@ especially important, as many parts of the standard library (including the
``ctypes`` module at runtime.
By default, Python will be compiled with an iOS deployment target (i.e., the
minimum supported iOS version) of 12.0. To specify a different deployment
minimum supported iOS version) of 13.0. To specify a different deployment
target, provide the version number as part of the ``--host`` argument - for
example, ``--host=arm64-apple-ios15.4-simulator`` would compile an ARM64
simulator build with a deployment target of 15.4.