The Android Workgroup is hosting another bi-weekly meeting 2026-05-06T16:00:00Z→2026-05-06T17:00:00Z. The workgroup meetings are free for anyone interested to join. Feel free to chime in, or just listen to the topics and discussions.
Post any topics you'd like to discuss here or on the Swift Open Source Slack.
As part of this topic, we should also discuss the new behavior of the swiftbuild system (which appears to be poised as the default build system in 6.4), and how it impacts the mechanics of how we will support packaging multi-architecture shared libraries into .apks.
As Marc said, swift-build is now the default build system in SwiftPM 6.4 and trunk 6.5, so we need to exercise it much more with the Android SDK snapshots and discuss how it affects many more areas than packaging and testing, making sure it ultimately does what we want.
For example, rather than run the included setup-android-sdk.sh script to tie the installed Android SDK to the wanted Android NDK, swift-build currently only supports invoking ANDROID_NDK_HOME=/home/finagolfin/android-ndk-r28c swift build --swift-sdk aarch64-unknown-linux-android28 ... to choose your NDK, ie through the environment variable.
We will expand that to include the now-working swift sdk configure subcommand also, for those who need more fine-grained NDK config, say in multi-NDK environs, and hope to throw out that extra NDK-tying setup script altogether with the upcoming 6.4 release.
We've had reports of Android apps shipping that were built by the official 6.3 release SDK, we should discuss what those devs are saying of the experience.