| commit | eb586efe6f4ee5ccac2f8eba8ca5cd2d1b112bbc | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Mon Feb 08 20:11:49 2021 -0500 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Thu Feb 11 19:06:09 2021 -0500 |
| tree | e2c6d96cbb783ef8c29a128b4d9d1878bec977e8 | |
| parent | 80ff46678055f82fa3000b8b5863c84f04be26f4 [diff] |
Check for existence of private key before generating OTA At the end of OTA generation, we will use some private key to sign the OTA payload. Since signing happens after the payload is being generated, if caller passes an incorrect key path, caller won't notice it until 1 hour later when delta_generator finishes. At which point caller has to staart from scratch, pass in another key path, and wait for an hour. Let's detect incorrect key path before calling delta_generator, so caller will get an error message right at beginning. Test: th Change-Id: Iefb1e0a9ed86f82664be1675afb84c020ec28fe7
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.