Lines Matching full:your
17 session for your NDK-generated machine code.</p>
24 <li>Build your app using the {@code ndk-build} script. The {@code ndk-gdb} script
26 <li>Enable app debugging in your {@code AndroidManifest.xml} file by including an
29 <li>Build your app to run on Android 2.2 (Android API level 8) or higher.</li>
32 API level that you declare in your {@code AndroidManifest.xml} file does not matter.</li>
33 <li>Develop your app in a Unix shell. On Windows, use <a href="https://www.cygwin.com/">Cygwin</a>
47 <p>Here, {@code $PROJECT} points to your project's root directory, and {@code $NDK} points to your
50 <p>When you invoke {@code ndk-gdb}, it configures the session to look for your source files
51 and symbol/debug versions of your generated native libraries. On successfully attaching to your
53 find various system libraries. This is normal, because your host machine does not contain
54 symbol/debug versions of these libraries on your target device. You can safely ignore these
71 <li>Checks that ADB is in your path.</li>
72 <li>Checks that your application is declared debuggable in its manifest.</li>
79 {@code --launch=<name>} option to automatically start your activity before the debugging
114 your app on the target device. You can override this default behavior by using {@code --start} to
118 in your application manifest. Use {@code --launch=<name>} to start the next launchable
126 activity from your application. This feature is only useful if your manifest defines multiple
132 <td><p>This convenience option prints the list of all launchable activity names found in your
152 tool executable. It is only necessary if you have not set your path to include that executable.</p>
162 several devices or emulators connected to your host machine. Their meanings are as follows:</p>
221 <p>If your app runs on a platform older than Android 2.3 (API level 9), {@code ndk-gdb}
