我无法在Windows调试的Android NDK应用程序。它seems它是在Windows上新线的问题
I can't debug android ndk app on Windows. It seems it is a new line problem on Windows
c:\Android\android-ndk-r9c\samples\hello-jni>..\..\ndk-build DUMP_APP_ABI
all
c:\Android\android-ndk-r9c\samples\hello-jni>
在Linux中,
hello-jni$ ../../ndk-build DUMP_APP_ABI
all
hello-jni$
有是继无行中的所有
在Linux
我使用未经修改 HELLO-JNI
从 Android的NDK-R9C
我也比较每个解压文件的大小,他们都是原创。它是干净的,从谷歌未经修改的NDK。它能够编译并做JavaDebug但不NativeDebug。 (在Windows上)
I also compared size of every unzipped file and they are original. It is clean unmodified NDK from Google. It is able to compile and do JavaDebug but not NativeDebug. (on Windows)
我的问题是:什么我做错了吗?是否有人可以证实,未改性的Android NDK R9C
(今天最新的)能够做本机调试与Eclipse + NDKPlugin。
My questions is: What I am doing wrong? Does someone can confirm that unmodifed Android NDK r9c
(latest today) is able to do native debugging with Eclipse+NDKPlugin.
PS 我忘了提,当我做本地调试,我得到
PS I forgot to mention that when I do Native Debug I get
[2013-11-18 14:38:50 - HelloJni] Unknown Application ABI:
[2013-11-18 14:38:50 - HelloJni]
[2013-11-18 14:38:50 - HelloJni] Unable to detect application ABI's
就像在that问题
我的理解是,这个问题是制作
所使用的 NDK -gdb
。参见 NDK-GDB在Windows :在cygwin时的制作
时,所有的好;如果cygwin的制作
未安装, NDK-GDB
失败。下面是总结 调试的Android NDK,在Windows
My understanding is that the the issue is which make
is used by ndk-gdb
. See ndk-gdb on windows: when cygwin's make
is used, all well; if cygwin make
is not installed, ndk-gdb
fails. Here is the summary from Debugging Android NDK, Under Windows:
的android:可调试=真正的
标志<应用
标签中的的AndroidManifest.xml 在 CMD (Windows的命令提示符):调用 NDK的构建
与 NDK_DEBUG = 1
在的cygwin bash下运行 NDK-GDB
add android:debuggable="true"
flag to <application
tag in AndroidManifest.xml
in cmd (windows' command prompt): invoke ndk-build
with NDK_DEBUG=1
in cygwin bash: run ndk-gdb