4 ms·
The NDK is a total 'bolt-on' solution to the problem, and support within the Android dev tools is basically non-existent. The biggest tragedy is that Google ha
by double051 12y ago
The NDK is a total 'bolt-on' solution to the problem, and support within the Android dev tools is basically non-existent.
The biggest tragedy is that Google had a chance to make a better NDK experience with Android Studio, but instead they chose to ignore it completely. With Eclipse you at least had an official add-on for NDK support, but now you're expected to manage it with your Gradle files by hand. Now, even more than before, you're at the whim of solutions on Stack Overflow.
- mdwrigh2 12y agoNDK support is being worked on. There are samples[1] of the API, but it's largely undocumented and still a work in progress. There's a reason AS hasn't hit 1.0 yet: it isn't ready. [1]: http://docs.google.com/viewer?a=v&pid=sites&srcid=YW5kcm9pZC5jb218dG9vbHN8Z3g6M2U0NDQ2YWFkYWVmNGY5NA http://docs.google.com/viewer?a=v&pid=sites&srcid=YW5kcm9pZC...
- pjmlp 12y agoI think having a few ex-Sun Java guys might have influenced that decision. Since all other mobile platforms offer better native support. This is just my personal opinion.