Some more topics:
-
Following on the move to build the trunk SDK against API level 24, plan any further Android API level changes.
-
The SwiftPM team are planning
swift sdkchanges that affect all SDKs, including of course Android, with one of those pulls just merged. Sound off on any further changes wanted, as Android users are likely the main users of this SwiftPM subcommand. -
Trunk SwiftPM just switched to swift-build as the default build system backend, which raises some issues for SDKs and Android, so we'll have to hash out how to approach that.
-
I'm told that some SwiftPM devs finally got the
swift sdksubcommand working on Windows, so we can reuse the trunk SDK bundles with the trunk Swift toolchain for Windows too. We should discuss how to handle that there may now be two ways to install differently-structured Android SDKs with the trunk Swift toolchain for Windows. -
We've been hitting some issues with the clang resource directory, a required directory from the clang toolchain for a platform, that we've been addressing in various ways. Explore if we can come up with a better way forward.
The call looks to have 4 topics already, so there may be no time to discuss this
I'm sure we can fit it in, we'll just need to prioritize and move topics around, plus make sure we don't go too long on any one topic.