Dan Albert
Dan Albert
We're more or less settled on making this an AAR rather than putting it in the NDK proper. The pieces for that are still coming together (and the testing work...
Sounds like a bug. Please file it.
It's a different sort of bug, but I think that is still a bug. Worth filing, I think (against the emulator, probably; they can redirect it if needed).
No. We'll close the bug when it's available. Some ICU APIs have been added to the platform in recent release but the wrapper that backports them is not currently being...
This thread links the prototypes we have. It's been long enough since I've looked at them that I can't really offer any help.
It's not something we currently have the resources to investigate for ndk-build. If you use CMake that doesn't matter: https://www.kitware.com/import-cmake-c20-modules/
You can use any CMake you like, it doesn't need to be in the SDK for you to use it: https://developer.android.com/studio/projects/install-ndk#vanilla_cmake (We know it's more convenient when it's in the...
(this bug is about ndk-build, if you want to continue discussing cmake, please take it to https://github.com/android/ndk/discussions)
> Are there any ideas on how FFI between wasm and native functions will work? AFAIK there are significant impedance mismatches between the two (e.g. wasm only has 32/64-bit integral...
> Does this mean a supposedly single device-agnostic libfoo.wasm shipped in a traditional APK format can be recompiled to native libfoo.so either by Play Store or on-device in the future?...