| commit | e7d0377f4af826fbc8f98864a01da835112e2f8c | [log] [tgz] |
|---|---|---|
| author | Tianjie <xunchang@google.com> | Wed Jul 14 15:56:37 2021 -0700 |
| committer | Tianjie <xunchang@google.com> | Wed Jul 14 16:07:33 2021 -0700 |
| tree | 99a9027a85d12ce741b854bfdeb5269f792a0937 | |
| parent | 69f66460deeef65f4120c0c05ac6a4c23d0af088 [diff] |
Write the vbmeta digest to the output zipfile also During signing, we write the entry directly to the output zip, intead of a temp directory. Add the logic to write vbmeta_digest.txt to output zipfile too. So the digest file will show up in the signed target files. Bug: 189926233 Test: add_img_to_target_files -a <target-files.zip> Change-Id: Ibf28a8f97512bda8c8c695e06190e1fb6573c53e (cherry picked from commit c3bf3d00a3077b66aa178f00fb789d34a042c9e8)
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.