Lines Matching full:build
51 includes all the tools you need to set up an Android project, build it, debug it and then
76 <dd>To compile and build your Android project into an installable .apk file.</dd>
91 with some default application files, stub files, configuration files and a build file.</p>
111 <li><code>target</code> is the "build target" for your application. It corresponds
113 build your project against. To see a list of available targets and their corresponding IDs,
117 for your .apk filename when you build your application.</li>
147 <li><code>build.xml</code> - Build file for Ant.</li>
148 <li><code>default.properties</code> - Properties for the build system. <em>Do not modify
150 <li><code>build.properties</code> - Customizable properties for the build system. You can edit
152 file to override default build settings used by Ant and provide a pointer to your keystore and key
154 so that the build tools can sign your application when built in release mode.</li>
157 <li><code>bin/</code> - Output directory for the build script.</li>
174 location of the SDK directory, because this will break the build scripts. (They
184 environment. You can also use this command to revise the build target of an existing project
198 <li><code>target</code> is the "build target" for your application. It corresponds to
200 like to build your project against. To see a list of available targets and their corresponding
222 <p>The Android build tools help you get started by automatically signing your .apk
223 files with a debug key at build time. This means
237 <p>There are two ways to build your application: one for testing/debugging your application
244 need to use the Ant tool to compile and build your project. This will create the .apk file
245 that is installed onto the emulator or device. When you build in debug mode, the .apk
249 When you build in release mode, the .apk file is <em>unsigned</em>, so you must manually
274 <p>For immediate application testing and debugging, you can build your application
275 in debug mode and immediately install it on an emulator. In debug mode, the build tools
281 <p>To build in debug mode:</p>
302 <p>When you're ready to release and distribute your application to end-users, you must build
309 build an unsigned package in release mode and then manually sign and align
310 the package, or allow the build script
313 <h4 id="ManualReleaseMode">Build unsigned</h4>
315 <p>If you build your application <em>unsigned</em>, then you will need to
318 <p>To build an <em>unsigned</em> .apk in release mode:</p>
339 <h4 id="AutoReleaseMode">Build signed and aligned</h4>
341 <p>If you would like, you can configure the Android build script to automatically
343 and the name of your key alias in your project's {@code build.properties} file. With this
344 information provided, the build script will prompt you for your keystore and alias password
345 when you build
349 you enter during the build process <strong>will be visible</strong>. If you are
353 perform the signing procedure manually, <a href="#ManualReleaseMode">build unsigned</a> and then
357 <p>To specify your keystore and alias, open the project {@code build.properties} file (found in the
366 <p>Save your changes. Now you can build a <em>signed</em> .apk in release mode:</p>
382 {@code build.properties} and aligned with {@code zipalign}. It's ready for
418 a target for your AVD that satisfies your application's build target (the AVD
446 first <a href="#Building">build your application</a>.</p>
467 directory after you <a href="#Building">build your application</a>.</p>
489 you can build your application and install it on the emulator in one simple step.
492 <code>ant install</code>. This will build your application, sign it with the debug key,
546 reference the library project and, at build time, include its compiled sources
580 application's build path, then building that application. </p>
582 <p>When you build an application that depends on a library project, the SDK
593 in each library. This lets you build up the resources actually used in your
599 priority by editing the application project's build properties. At build time,
604 and that, at build time, library projects are <em>not</em> merged with each
616 <p>Android library projects are a build-time construct, so you can use them to
617 build a final application <code>.apk</code> that targets any API level and is
671 structure that includes preset property that indicates to the build system that
708 <p>If you want to update the build properties (build target, location) of the
722 the library project in the application project's build properties.</p>
734 <p>This command updates the application project's build properties to include a
768 <p>At build time, the libraries are merged with the application one at a time,
770 itself reference another library and that, at build time, libraries are not
806 <p>To build an application project that depends on one or more library projects,
807 you can use the standard Ant build commands and compile modes, as described in
847 you build the dependent application project, the tools automatically locate and
854 must build against a target that includes the external library (for example, the
895 <p>When you build the dependent application project, the code of any libraries
