Skip to content

[android] Support building _CFPosixSpawnFileActionsChdir() for older Android APIs too #5210

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

finagolfin
Copy link
Member

@jakepetroules, following on the similar swiftlang/swift-llbuild#985, this gets Foundation building with older Android APIs too, which I've had to patch otherwise on my Android CI that builds against API 24.

@finagolfin
Copy link
Member Author

@swift-ci test

@finagolfin
Copy link
Member Author

This pull has no effect outside Android: the linux CI appears broken right now, as prior CI runs for unrelated pulls fail with the same error.

…r Android APIs too

Phase out the existing Android scheme of adding different callbacks based on
whether the posix_spawn APIs are there at runtime, by simply linking against
them at compile-time instead if a build triple with API 28 or later is specified.
@finagolfin
Copy link
Member Author

Updated this to actually build when the Android API is greater than 27 and added a default _CFPosixSpawnFileActionsChdir() for the previous callback scheme.

@marcprux and @compnerd, I've only tested the old callback scheme on my Android CI, as it builds against API 24, so if you two are building against API 28 or later, please build this and let me know what you think.

@parkera
Copy link
Contributor

parkera commented May 13, 2025

@swift-ci test

@finagolfin
Copy link
Member Author

@swift-ci test

@finagolfin
Copy link
Member Author

I just built and tested this natively on Android against API 28, got the same test results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants