Yeah, I have no intention of spending any serious amount of time debugging Android NDK code with Eclipse, fortunately the backwards and forwards compatibility on the platform seems rock-solid and the native code compiler is offering no surprises at all so far.Spike wrote:if you can run the same code on windows/linux and get proper stack traces for crashes there instead, then its just much simpler that way instead of trying to get the user to figure out how to use a shell/adb/logcat stuff.
Immediate to-do: clock, input, "window" setup (onPause/onResume, etc.), downloads and figuring out where downloaded files get stored.