Lines Matching full:build
13 <li><a href="#signing">Signing a build for release</a></li>
26 <p>These keys are used to sign applications separately for release images and are not used by the Android build system. The build system signs packages with the testkeys provided in <code>build/target/product/security/</code>. Because the testkeys are part of the standard Android open source distribution, they should never be used for production devices. Instead, device manufacturers should generate their own private keys for shipping release builds.</p>
59 <h3>Signing a build for release</h3>
60 <p>Signing a build for a release is a two-step process. </p>
62 <li>Sign all the individual parts of the build.</li>
66 <p>Use <code>build/tools/releasetools/sign_target_files_apks</code> to sign a <code>target_files</code> package. The <code>target_files</code> package isn't built by default, you need to make sure to specify the "dist" target when you call make. For example:</p>
73 ./build/tools/releasetools/sign_target_files_apks -d vendor/<vendor_name>/security/<product_name> <product_name>-target_files.zip signed-target-files.zip
75 <p>If you have prebuilt and pre-signed apk's in your build that you don't want re-signed, you must explicitly ignore them by adding <code>-e Foo.apk=</code> to the command line for each apk you wish to ignore.</p>
80 build/tools/releasetools/img_from_target_files signed-target-files.zip signed-img.zip