Skip to content
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

Add Android release binaries to CI #8601

Merged

Conversation

alexcrichton
Copy link
Member

This commit is inspired by #6480 and historical asks for Android binaries. This does the bare minimum necessary to configure C compilers such that we can produce binaries but I'll admit that I'm no Android developer myself so I have no idea if these are actually suitable for use anywhere. Otherwise though this build subsumes the preexisting check in CI that the build works for Android, so that part is removed too.

This additionally changes how the NDK is managed from before. Previously a GitHub Action was used to download Java and the NDK and additionally used the cargo ndk subcommand. That's all removed now in favor of configuring C compilers directly with a pre-installed version of the NDK which should help reduce the CI dependencies a bit.

This commit is inspired by bytecodealliance#6480 and historical asks for Android
binaries. This does the bare minimum necessary to configure C compilers
such that we can produce binaries but I'll admit that I'm no Android
developer myself so I have no idea if these are actually suitable for
use anywhere. Otherwise though this build subsumes the preexisting check
in CI that the build works for Android, so that part is removed too.

This additionally changes how the NDK is managed from before. Previously
a GitHub Action was used to download Java and the NDK and additionally
used the `cargo ndk` subcommand. That's all removed now in favor of
configuring C compilers directly with a pre-installed version of the NDK
which should help reduce the CI dependencies a bit.
@alexcrichton alexcrichton requested a review from a team as a code owner May 12, 2024 17:10
@alexcrichton alexcrichton requested review from fitzgen and removed request for a team May 12, 2024 17:10
Copy link
Contributor

@jameysharp jameysharp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I worry somebody might think we consider Android a tier 1 platform or something if we start having builds in the releases, but we can navigate that confusion if it happens. I have a couple small suggestions but this seems reasonable to me!

.github/actions/android-ndk/action.yml Outdated Show resolved Hide resolved
@alexcrichton
Copy link
Member Author

True! I've also updated the tier listing to explicitly say that this is tier 3, like riscv64.

Part of my own motivation here is that I get the impression folks will glance at the release binaries and determine our platform support without digging much further, so this might help give the impression that Wasmtime isn't ONLY windows/mac/linux, perhaps. There's only so much we can do with that level of review from a prospective user though.

@alexcrichton alexcrichton enabled auto-merge May 13, 2024 15:08
@alexcrichton alexcrichton added this pull request to the merge queue May 13, 2024
Merged via the queue into bytecodealliance:main with commit d74b34f May 13, 2024
22 checks passed
@alexcrichton alexcrichton deleted the build-android-binaries branch May 13, 2024 15:47
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