Lines Matching refs:debug
12 <li><a href="#DebugMode">Building in debug mode</a></li>
51 includes all the tools you need to set up an Android project, build it, debug it and then
220 with a <em>debug key</em> (for immediate testing on an emulator or development device)
224 files with a debug key at build time. This means
228 own private key, rather than the debug key generated by the SDK tools. </p>
239 — <em>debug mode</em> — and one for building your final package for release —
244 <p>Whether you're building in debug mode or release mode, you
246 that is installed onto the emulator or device. When you build in debug mode, the .apk
247 file is automatically signed by the SDK tools with a debug key, so it's instantly ready for
259 debug mode.</p>
273 <h3 id="DebugMode">Building in debug mode</h3>
276 in debug mode and immediately install it on an emulator. In debug mode, the build tools
277 automatically sign your application with a debug key and optimize the package with
282 <p>To build in debug mode:</p>
286 <li>Use Ant to compile your project in debug mode:
287 <pre>ant debug</pre>
288 <p>This creates your debug .apk file inside the project <code>bin/</code>
289 directory, named <code><em><your_project_name></em>-debug.apk</code>. The file
290 is already signed with the debug key and has been aligned with {@code zipalign}.</p>
467 <p>Your APK file (signed with either a release or debug key) is in your project {@code bin/}
493 <code>ant install</code>. This will build your application, sign it with the debug key,
917 <p>This section describes how to display debug information on the screen (such
918 as CPU usage), as well as how to hook up your IDE to debug running applications
935 about <a href="{@docRoot}guide/developing/debug-tasks.html#ide-debug-port">