Hi all, I've been dabbling with Android Studio 1.3 RC 3 for a small test project. Our apps tend to be mainly native code, so NDK support is crucial before a full switch to Studio.
The test project I'm using shows some promise over the Eclipse-based solution - I love the "context" drop-down to switch between the different build configs for preprocessor defines etc, and the intellisense seems better than Eclipse (where I constantly struggle to get the C++ indexer set up properly). The tooling around JNI methods (as demoed in the I/O video) is really cool too, and makes it feel like Google are recognising that JNI is an important part of many Android projects. The native debugging experience has always been flaky with Eclipse, and I was hoping the Studio support would provide a good improvement here. It was unfortunate to discover that it still requires a separate "Native Debug" configuration. Under Eclipse it was possible to launch with native debugging, then also attach the Java debugger from the processes view on Android. Breakpoints on either side were then correctly hit, but stepping through from Java to Native didn't work. This trick doesn't seem to work on Android Studio, continuing from the Java side seems to just hang the debugger, rather than triggering the next breakpoint on the Native side. Can you share any tips or plans around this support - jumping from Java to Native is great at the source code editor level, but if anything I'd suggest it's even more important at debug time. Ideal of course would be integrating the native and java list of frames, and having a single debug view. Any hope of that? Thanks Simon -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
