ndk
ndk copied to clipboard
rust-mobile
Rust bindings to the Android NDK
https://github.com/rust-windowing/android-ndk-rs/blob/f24606cc840af2f97f0daebe1e2e7cd3aca52287/ndk/src/aaudio.rs#L545-L565 If `callback` panics and unwinds, `ffi_callback` unwinds, which is [undefined behaviour](https://doc.rust-lang.org/nomicon/unwinding.html). > Rust's unwinding strategy is not specified to be fundamentally compatible with any other language's unwinding. As such,...
Moving this into separate issue to increase discoverability. > 1. I (and hopefully I'm not alone) should check out your tool and evaluate how much all the extra automation improves...
Fixes #154 ~When an application returns its control flow back from `main()` it is generally assumed to be done polling on the looper and wishes to terminate. Android is made...
This has caused my app to work when built locally, but not when built by GitHub Actions, as that still defaults to 21.4.7075529. See: https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-Readme.md#environment-variables-3 See the last 8-10 lines...
We have some tcp services that we connect to at startup, the easiest way to do that would be to set up reverse port forwarding through adb reverse when invoking...
Having multiple versions of ndk-glue in the dependency tree leads to crashes because of uninitialized `NATIVE_ACTIVITY`. Example: Including ndk-glue 0.5. When entering `main()`, `NATIVE_ACTIVITY` 0.5 gets initialized. Including Oboe crate...
Hello i'm trying to declare another activity in the manifest so i can call it using jni, but right now i think (and i may be wrong) Cargo.toml right now...
I get a `Didn't find Cargo.toml` error in `cargo-subcommand`, so it's not really a bug in `cargo-apk`. However since `cargo-apk` is the only user it might make sense to move...
When running commands such as `cargo apk help` or the upcoming `cargo apk version`, which should run _anywhere_ and **don't depend on the workspace in `$PWD`**, `cargo-apk` still exits with...
cargo-apk should be able to use features (and maybe targets) to conditionally build the `AndroidManifest.xml`, in a similar way to gradle build flavors. My use-case is having different `runtime_libs` for...