e924df0e1a
# Objective Add two features to switch bevy to use `NativeActivity` or `GameActivity` on Android, use `GameActivity` by default. Also close #12058 and probably #12026 . ## Solution Add two features to the corresponding crates so you can toggle it, like what `winit` and `android-activity` crate did. --- ## Changelog Removed default `NativeActivity` feature implementation for Android, added two new features to enable `NativeActivity` and `GameActivity`, and use `GameActivity` by default. ## Migration Guide Because `cargo-apk` is not compatible with `GameActivity`, building/running using `cargo apk build/run -p bevy_mobile_example` is no longer possible. Users should follow the new workflow described in document. --------- Co-authored-by: François Mockers <francois.mockers@vleue.com> Co-authored-by: BD103 <59022059+BD103@users.noreply.github.com> Co-authored-by: Rich Churcher <rich.churcher@gmail.com>
22 lines
508 B
TOML
22 lines
508 B
TOML
[package]
|
|
name = "bevy_mobile_example"
|
|
# Version is required by `cargo-apk`, though this value will never change.
|
|
version = "0.0.0"
|
|
edition = "2021"
|
|
description = "Example for building an iOS or Android app with Bevy"
|
|
publish = false
|
|
license = "MIT OR Apache-2.0"
|
|
|
|
[lib]
|
|
name = "bevy_mobile_example"
|
|
crate-type = ["staticlib", "cdylib"]
|
|
|
|
[dependencies]
|
|
bevy = { path = "../../" }
|
|
|
|
[target.aarch64-apple-ios-sim.dependencies]
|
|
bevy = { path = "../../", features = ["ios_simulator"] }
|
|
|
|
[lints]
|
|
workspace = true
|