| commit | 38888d390f299ac576b3145b520cda2dcb897095 | [log] [tgz] |
|---|---|---|
| author | Daniel Norman <danielnorman@google.com> | Thu Nov 19 14:51:15 2020 -0800 |
| committer | Daniel Norman <danielnorman@google.com> | Thu Nov 19 14:51:15 2020 -0800 |
| tree | c01451a4e605287ca64403d83b0ab6d0015eee6a | |
| parent | ad33b891f8313a5379f1e69f17bbde3ec899bfdc [diff] |
Turns on building vbmeta.img when merging if avb_enable=true.
Needed after commit 8218225794c50a44de1fa5fe3257b8973a510bf7
which skips regenerating vbmeta.img if avb_building_vbmeta_image!=true.
Partial builds that disable vbmeta generation do not set this field.
Bug: 169892879
Test: Run merge_target_files.py on builds that have avb_enable=true but
PRODUCT_BUILD_VBMETA_IMAGE=false. Observe vbmeta.img generation.
Change-Id: Id498dbd28c909e19cd35178b95a0b5dc22a1ac70
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.