| commit | b81b4e3621d3917c43e19ae99560ac67a5150a7a | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Tue Jan 10 10:37:56 2023 -0800 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Thu Jan 12 17:34:42 2023 -0800 |
| tree | 75ef40df5bccc3c7e9cec50f99571978dcdf18a8 | |
| parent | a10528c7a80da9389a84039b45e64ba126908f71 [diff] |
Allow vendors to add custom vbmeta partitions Currently we only have vbmeta_system and vbmeta_vendor. Add BOARD_AVB_VBMETA_CUSTOM_PARTITIONS , which allows OEMs to define their own vbmeta_*.img partitions. example: aosp/2381823 Bug: 263568805 Change-Id: Id671e2c3aee9ada90256381cce432927df03169b
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.