Skip to content

gh-138171: Migrate iOS testbed location and add Apple build script #138176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
freakboy3742 merged 17 commits into from
Sep 19, 2025
Merged

gh-138171: Migrate iOS testbed location and add Apple build script #138176

Changes from 1 commit
Commits
Show all changes
17 commits
Select commit Hold shift + click to select a range
4a11615
Migrate testbed location and add cross-platform build script.
freakboy3742 Aug 21, 2025
b89f46f
As a buildbot workaround, retain a copy of the compiler shims in the …
freakboy3742 Aug 27, 2025
68d671b
...and get the legacy location correct.
freakboy3742 Aug 27, 2025
39856d1
Updates to CODEOWNERS, gitignore and clean targets.
freakboy3742 Aug 27, 2025
f6a836c
Apply suggestions from code review
freakboy3742 Aug 28, 2025
c692e9a
Convert README to Markdown.
freakboy3742 Aug 29, 2025
fe39aa4
Add type hints and more docstrings.
freakboy3742 Aug 29, 2025
ceff927
Minor markdown fixes.
freakboy3742 Aug 29, 2025
2208323
Merge branch 'main' into apple-build
freakboy3742 Sep 10, 2025
e856075
Corrected minor typos found in review.
freakboy3742 Sep 10, 2025
2606b8f
Correct handling of pre-release Python versions.
freakboy3742 Sep 10, 2025
2114dd5
Remove redundant copies of the standard library.
freakboy3742 Sep 17, 2025
d56a3de
Update documentation to reflect new install entry script.
freakboy3742 Sep 17, 2025
611d82b
Merge branch 'main' into apple-build
freakboy3742 Sep 17, 2025
4feeabe
Correct handling of --fast-ci and --slow-ci options.
freakboy3742 Sep 17, 2025
ebbbf32
Restore the CODEOWNERS entry for the top level iOS folder.
freakboy3742 Sep 17, 2025
e0f6b5a
Move build script into stub XCframework so that 'make testios' has ac…
freakboy3742 Sep 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Minor markdown fixes.
  • Loading branch information
@freakboy3742
freakboy3742 committed Aug 29, 2025
commit ceff9278d237b4dfcffe1ffe359c548ec284890a
32 changes: 16 additions & 16 deletions Apple/iOS/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ Python build for a single framework, the following options are available.

Specify the name for the Python framework; defaults to `Python`.

> [!Note]
> [!NOTE]
> Unless you know what you're doing, changing the name of the Python
> framework on iOS is not advised. If you use this option, you won't be able
> to run the `Apple` build script without making significant manual
Expand All @@ -119,14 +119,14 @@ provide the `--enable-framework` flag when configuring the build. The build
also requires the use of cross-compilation. The minimal commands for building
Python for the ARM64 iOS simulator will look something like:
```
export PATH="$(pwd)/Apple/iOS/Resources/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin"
./configure \
--enable-framework \
--host=arm64-apple-ios-simulator \
--build=arm64-apple-darwin \
--with-build-python=/path/to/python.exe
make
make install
export PATH="$(pwd)/Apple/iOS/Resources/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin"
./configure \
--enable-framework \
--host=arm64-apple-ios-simulator \
--build=arm64-apple-darwin \
--with-build-python=/path/to/python.exe
make
make install
```

In this invocation:
Expand Down Expand Up @@ -237,9 +237,9 @@ To run the test suite, configure a Python build for an iOS simulator (i.e.,
`PATH` has been configured to include the `Apple/iOS/Resources/bin` folder and
exclude any non-iOS tools, then run:
```
make all
make install
make testios
make all
make install
make testios
```

This will:
Expand Down Expand Up @@ -267,7 +267,7 @@ testbed will be created in a directory named

You can generate your own standalone testbed instance by running:
```
python cross-build/iOS/testbed clone my-testbed
python cross-build/iOS/testbed clone my-testbed
```

In this invocation, `my-testbed` is the name of the folder for the new
Expand All @@ -276,7 +276,7 @@ testbed clone.
If you've built your own XCframework, or you only want to test a single architecture,
you can construct a standalone testbed instance by running:
```
python Apple/testbed clone --platform iOS --framework <path/to/framework> my-testbed
python Apple/testbed clone --platform iOS --framework <path/to/framework> my-testbed
```

The framework path can be the path path to a `Python.xcframework`, or the
Expand All @@ -286,7 +286,7 @@ You can then use the `my-testbed` folder to run the Python test suite,
passing in any command line arguments you may require. For example, if you're
trying to diagnose a failure in the `os` module, you might run:
```
python my-testbed run -- test -W test_os
python my-testbed run -- test -W test_os
```

This is the equivalent of running `python -m test -W test_os` on a desktop
Expand All @@ -297,7 +297,7 @@ they were arguments to `python -m` on a desktop machine.

You can also open the testbed project in Xcode by running:
```
open my-testbed/iOSTestbed.xcodeproj
open my-testbed/iOSTestbed.xcodeproj
```

This will allow you to use the full Xcode suite of tools for debugging.
Expand Down
Loading