| commit | 6d8ec5803b8387f2aa51e999b51b8f755ed996d2 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Tue Jun 12 14:53:12 2018 -0700 |
| committer | Tao Bao <tbao@google.com> | Tue Jun 12 15:04:08 2018 -0700 |
| tree | 2b954ad330901a2dd88e81879fc866ba93971a6c | |
| parent | e59bb32cb7f7f2eab6628b34ba71d583baa0ec3e [diff] |
releasetools: Explicitly pass the SHA-1 of source boot image to PatchCheck. Although the SHA-1 of the source boot image has been encoded in the filename, the updater code currently doesn't extract that and would fail to find a matching backup from /cache. This could lead to corrupt install, if it's interrupted while patching the boot image. Bug: 80630342 Test: Generate an non-A/B incremental package. Verify the script. Change-Id: Ie2b1a90836c3ccb4758e1a2d9b69a88de94ae0c7
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.