mirror of
https://github.com/rust-mobile/android-activity.git
synced 2026-07-11 17:18:55 +00:00
b161b24ce4
In Winit then we ideally want to be able to associate a cloned reference to the AndroidApp with the `Window` and `MonitorHandle` types (since that's the most practical way to access the native_window and config state for the application) but for that `AndroidApp` needs to be Send + Sync
This tests using GameActivity with winit and wgpu.
This is based on a re-worked winit backend here: https://github.com/rib/winit/tree/android-activity
Although it would have been possible to handle the suspend/resume lifecycle events with a simpler approach of destroying and recreating all graphics state, this tries to represent how lifecycle events could be handled in more complex applications, such as within Bevy.
Considering that lifecycle events aren't supported consistently on desktop platforms this test also aims to build and run on desktop - for the sake of testing how more complex applications (that need to be portable) can work. (enable "desktop" feature to build binary)
export ANDROID_NDK_HOME="path/to/ndk"
export ANDROID_HOME="path/to/sdk"
rustup target add aarch64-linux-android
cargo install cargo-ndk
cargo ndk -t arm64-v8a -o app/src/main/jniLibs/ build
./gradlew build
./gradlew installDebug
adb shell am start -n co.realfit.agdkwinitwgpu/.MainActivity