| commit | bbde59f9eb656f6150815b6a74f95273c646dc35 | [log] [tgz] |
|---|---|---|
| author | Tianjie <xunchang@google.com> | Mon May 03 21:18:56 2021 -0700 |
| committer | Tianjie Xu <xunchang@google.com> | Wed May 05 18:04:51 2021 +0000 |
| tree | e19351d4ae2523f624009afdb1461fd2f19515cd | |
| parent | bf7d6d78c7cb205ede424da0925c7dc9ae39f53b [diff] |
Calculate the vbmeta digest when building images Calculate the vbmeta digest if the device builds vbmeta image. The digest will used later to determine the build fingerprint in new format. One sample usage is the ota package generation, where we put the build fingerprint in the ota metadata. But we don't have the runtime vbmeta digest provided the bootloader. Bug: 186786987 Test: unit tests Change-Id: If572e2b973e295a6c95a9e23a65bb20b3afbf1b0
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.