| commit | 276f06275b3c93bbebf787bb6ffb28fce9ee3fee | [log] [tgz] |
|---|---|---|
| author | Daniel Norman <danielnorman@google.com> | Fri Jul 26 14:13:51 2019 -0700 |
| committer | Daniel Norman <danielnorman@google.com> | Fri Aug 02 20:13:03 2019 +0000 |
| tree | df2ad5d0f93ea7c0fab91b662f8677af751b0b82 | |
| parent | c016c281c1f34aa2d9507cc8f2174b3ce52f4cbb [diff] |
Adds support for optionally generating vbmeta.img in merge_builds. Bug: 137853921 Bug: 138671115 Test: python -m unittest test_common Test: python -m unittest test_add_img_to_target_files Test: Ran 'merge_builds --build_vbmeta' for two devices, one with the vbmeta struct on system.img and another with vbmeta_system.img. Flashed the regenerated vbmeta.img files on devices, devices boot. Change-Id: I8d7585c7af468be3d242d8aceeed6d27e6fc6d96
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.