Lines Matching refs:package
36 …final package for release — <em>release mode</em>. Regardless of which way you build your ap…
73 application with a debug key and optimize the package with {@code zipalign}.</p>
92 <p>Each time you change a source file or resource, you must run Ant again in order to package up
105 resulting application package with your private key, and should then align it using the {@code
106 zipalign} tool. There are two approaches to building in release mode: build an unsigned package
107 in release mode and then manually sign and align the package, or allow the build script to sign
108 and align the package for you.</p>
113 the package.</p>
144 your application package. To do so, you must provide the path to your keystore and the name of
147 mode and produce your final application package, which will be ready for distribution.</p>
242 This is because the package manager usually examines manifests completely only on emulator
334 <dd>Builds a debug package. Works on application, library, and test projects and compiles
342 <dd>Builds a release package.</dd>
346 <dd>Builds an instrumented debug package. This is generally called automatically when building a
351 <dd>Builds and installs a package. Using <code>install</code> by itself fails.</dd>
354 <dd>Installs an already compiled debug package. This fails if the <code>.apk</code> is not
358 <dd>Installs an already compiled release package. This fails if the <code>.apk</code> is not
362 <dd>Installs an already compiled test package. Also installs the <code>.apk</code> of the
366 <dd>Installs an already compiled instrumented package. This is generally not used manually as
367 it's called when installing a test package. This fails if the <code>.apk</code> is not already