33 ms·
to be clear, this is only really useful for applications that present their ui through opengl and do not interact with the rest of the android system very much.
by a-dub 2y ago
to be clear, this is only really useful for applications that present their ui through opengl and do not interact with the rest of the android system very much.
the ndk is meant for writing little bits of c to speed things up in a classic java android application.
this is a pretty cool hack that allows for opengl apps to be written in straight c that run full screen and have limited access to things like keyboards, adc inputs or usb.
it does not include a reimplementation of the android frameworks in c and the ndk provides limited access for ndk code to interact with them.
the main use case seems to be supporting a program for live audio reactive visuals based on extraction of chroma.
- mavamaarten 2y agoI read that last bit of your comment before I opened the link, and thought to myself, that's something Cnlohr would write. And it is! Hah.
- spookie 2y agoTo be fair this is the way to not be platform dependent and more people should pursue it. I'm doing a desktop app meant to be as cross compatible as possible and the only reasonable way to do it (without sending yourself into build config hell) is with opengl.
- marcellus23 2y agoHow do you make it accessible?
- kllrnohj 2y ago> this is a pretty cool hack that allows for opengl apps to be written in straight c that run full screen and have limited access to things like keyboards, adc inputs or usb. It's not even a hack. Android NDK added that way back in like gingerbread, it's just a NativeActivity. https://developer.android.com/ndk/samples/sample_na https://developer.android.com/ndk/samples/sample_na This is just a small framework on top of that. It's not doing anything "new"
- a-dub 2y agoit is, however, cross platform for a handful of embedded targets of which android is one of.