Is this in a state to be used in place of cargo-apk?

[sinoth]

Currently writing a VR game for the Quest 2 which uses cargo-apk. Saw the deprecation warning and checked out this tool, but there is no documentation for those of us coming from cargo-apk and wildly different tooling / system requirements (like needing the clang toolchain).

Has anyone converted their project over from cargo-apk?

Previously with ndk-glue and cargo-apk, there was no need for gradle but is gradle the recommended way to handle this now? An example: https://github.com/rust-mobile/rust-android-examples/tree/main/na-openxr-info

[dvc94ch]

You always need the clang toolchain to compile c code. We just use your distro's clang instead of the one bundled with the sdk

[sinoth]

I'm looking at this as a user of cargo-apk. Cross-compiling Rust to Android from my Windows machine didn't require much past some environment variables pointed to the Android SDK and NDK. In comparison my x doctor is very unhappy.

In any case, I'm a fish out of water here... it seems cargo-apk's method of supplying Android settings via Cargo.toml has also changed, but I can't find documentation for that anywhere. Are there better docs or examples somewhere I'm missing?

[andraantariksa]

Sadly, this project not on par with cargo-apk. For now (0.2.0) it only supports these arch

Build artifacts for target arch. Can be one of `arm64` or `x64`