![]() ![]() On Android/NDK, on crashes, even if you don't get full stack trace, can you at least get a file name / line number before program dies? Then I can print out a file name / line number before it dies. In wasm32, I use set panic hook to capture panics. If you've any more questions please let me know I'll try to answer them based on my experience. I'm not quite sure what you mean by the android 'native' API, since there's the NDK (native development kit), and the JNI (java native interface).Ī noteworthy point to make though is that given the progress made in cargo-apk, I can have a java-less codebase, so I don't have to juggle languages. And since egl isn't a very nice interface to work with, I was left with println debugging. I was stuck trying to debug an glutin for a week only to find it was a debug flag that was wrecking everything. The biggest obstacle in developing on Android I have faced is not knowing what the obstacle was.Which can unfortunately lead to some ugly code. Because, as mentioned earlier, the NDK provides essentially event handling, the rest, more complicated things you'd want to do are left up to you using the JNI. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |