commit | 81f39298671e9d1885076f9d2c3e401ef3a5715b | [log] [tgz] |
---|---|---|
author | Hung-ying Tyan <tyanh@google.com> | Thu Jul 30 22:12:14 2020 +0800 |
committer | Hung-ying Tyan <tyanh@google.com> | Fri Jul 31 18:59:40 2020 +0800 |
tree | 0d4ba7ace3e704cbc7e1ad6e0ce3e033c27384f8 | |
parent | c8343a3f0e1552bfa2d744adfdfbee2907464348 [diff] |
Remove vbmeta_system from GSI targets This partially reverts commit 1785816ca1cfeaf2ce602e0b704ea5ba262144e3 so that the hash tree at the end of GSI is properly signed by AVB. Bug: 161503491 Test: 'm dist' and check that vbmeta_system.im is gone Test: boot GSI on android10 CF Test: 'avbtool info_image --image system.img' and check AVB signing Change-Id: I9f488380c0c410fdbd02c3c0803b6dc06cf7faab
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.