ndk-glue suffers one fatal flaw: it's "only" supposed to be used by the crate providing fn main() and only supposed to end up in the dependency graph once as it has static globals which get duplicated across versions.
Introducing ndk-context: a crate that holds these statics, with the intention/premise to not see a breaking release /ever/ and make this a problem of the past. The crate is currently initialized with the VM and Android Context on ndk-glue 0.5.1 and 0.6.1 making it compatible with whatever is current, and the possibility for backporting to older ndk-glue versions too.
kornelski
commented
2 years ago
ndk-gluesuffers one fatal flaw: it's "only" supposed to be used by the crate providingfn main()and only supposed to end up in the dependency graph once as it hasstaticglobals which get duplicated across versions.In the current case with
winit 0.26still onndk-glue 0.5butapp_dirs2booted from0.4to0.6it'll always panic infn native_activity()as thestaticglobals on these versions are not initialized: https://github.com/app-dirs-rs/app_dirs2/pull/18#issuecomment-1029026065Introducing
ndk-context: a crate that holds thesestatics, with the intention/premise to not see a breaking release /ever/ and make this a problem of the past. The crate is currently initialized with the VM and Android Context onndk-glue0.5.1 and 0.6.1 making it compatible with whatever is current, and the possibility for backporting to olderndk-glueversions too.See also: https://github.com/rust-windowing/android-ndk-rs/issues/211 https://github.com/rust-windowing/android-ndk-rs/pull/223