@mishal_shah joined us for this video-conference meeting at our usual bi-weekly time. Here's the agenda we discussed, along with the outcomes:
-
Put together a public roadmap: this will tell interested users what's coming next and will consist mostly of the following agenda items. We've setup a github project for Android that we will start populating in the coming weeks.
-
Produce an official Android SDK: The Browser Company (TBC) is looking at including official trunk Android SDKs in the Windows toolchain, and @marcprux and @Finagolfin will submit a linux Dockerfile that produces an official Android SDK bundle for the 6.2 and trunk branches, with the Swift runtime built against API 28, for the
posix_spawn
APIs, but allowing packages to be built against any subsequent API. FoundationXML and FoundationNetworking will most likely also be included. -
@marcprux is working on slimming the multi-arch Swift runtime size by separating out ICU data. We agreed to keep pushing on that and upstream it as a build option at least, then integrate it with the Android SDK if all goes well.
-
Increase official CI testing for Android: @compnerd from TBC is considering adding Android testing on the Windows CI and @Finagolfin plans to submit a linux Dockerfile for Android to the official CI and fix some of the currently failing compiler validation tests. We discussed getting the Android emulator running on various CI, and nested virtualization issues which mean it works in some CI environments and not others.
-
Put together an official github workflow or CI for Swift packages to build and test against the official Android SDK: while we cannot fully set this up till the official SDK is ready, we can certainly start working on it simultaneously. Marc is talking to Dave at the Swift Package Index about adding Android build info, similar to how it reports support for other platforms.
-
Discussion is going on outside this workgroup on swift-java interop, including about standardization, which some members will keep us updated on.
-
Marketing Swift on Android: TBC has done a great job of writing about their work on the Windows port and even doing videos about it, we would similarly like to blog about our work on this Android port. Mishal said that once we submit a blog post, we can discuss the publishing venue for that further.
-
Debugging was a big priority in previous meetings, so we followed up on how things are going and more work will be done on streamlining what we have so far.
If you would like to help out with any of these initiatives, don't hesitate to reach out to us.