Coordinate Android NDK update with winit 0.27

[msiglreith]

https://github.com/rust-windowing/winit/issues?q=is%3Aopen+label%3A%22platform%3A+Android%22+milestone%3A%22Version+0.27%22+

• Release ndk-sys-0.4.0, ndk-0.7.0, ndk-glue-0.7.0 rust-mobile/ndk#314 Coordinate with the release of ndk 0.7.0 (breaking changes: https://github.com/rust-windowing/android-ndk-rs/blob/master/ndk/CHANGELOG.md) prior to releasing winit (seems like a nice cut-off point);
• Alongside the update, re-exporting ndk-glue would be helpful under the light of Adds Android winit<->ndk_glue version match table #1993
  • Consider extending ndk_context instead and automagically support a wider range of ndk-glue versions?
  • Alternatively there have been suggestions [TODO: reference needed] of reworking how ndk-glue passes its structs to the user and removing static globals plus their accessor functions;
• Use NativeWindow's RawWindowHandle implementation directly: ndk: Implement HasRawWindowHandle directly on NativeWindow rust-mobile/ndk#274
• android: Hold NativeWindow lock until after notifying the user with Event::Suspended #2307
• ndk-glue: Switch to parking_lot for mappable and Sendable lock guards rust-mobile/ndk#282
• ndk-glue: Replace ancient lazy_static crate with once_cell rust-mobile/ndk#285
• cargo-apk,ndk-build: Move NDK r23 -lgcc workaround to cargo_ndk to reuse in -- subcommand rust-mobile/ndk#286
• cargo-apk: Append --target to blanket cargo apk -- calls when not provided rust-mobile/ndk#287
• ndk-glue: Wrap NativeWindow/InputQueue locks in a newtype rust-mobile/ndk#288
• Fix winit CI failures on Android: Release ndk-build-0.6.0, cargo-apk-0.9.2 rust-mobile/ndk#289
• ndk: Move library documentation to modules rust-mobile/ndk#290
• ndk: Replace posix module with std::io::Error::from_raw_os_error rust-mobile/ndk#291
• ndk/input_queue: Replace InputQueueError with std::io::Error and add missing docs rust-mobile/ndk#292
• Enable doc_cfg and doc_auto_cfg for all [features] crates on https://docs.rs rust-mobile/ndk#293
• ndk/input_queue: Remove Result wrapping from has_events() rust-mobile/ndk#294
• ndk: Replace HardwareBufferError with std::io::Error through new helper conversion function rust-mobile/ndk#295
• ndk: Fix HardwareBuffer leak for AndroidBitmap and clarify handling in docs rust-mobile/ndk#296
• ndk: Remove "irrelevant" hardware_buffer/trace feature in favour of API level rust-mobile/ndk#320

[msiglreith]

Some thoughts on the second point regarding re-exporting: #2047 (comment)

[MarijnS95]

@msiglreith Is this issue now used as tracking for Winit 0.27? If so, I think we should add the following entries:

[EDIT: Moved to original post]

[MarijnS95]

@msiglreith Given your thumbs-up I've moved the entries into your top-post so that they get counted towards the number of tasks, and renamed the title to state that we'd like to sync up with 0.27.

I have a few other breaking changes in mind that require coordination between winit and the ndk, so it'd be great if we can bump ndk->winit->glutin in that order when the time comes to it. So a request to the winit maintainers to ping me (in this issue) whenever plans are commencing to set out 0.27 :)