commit | 679242b8778e738ac87f8f06d3f339a0eee6aa9e | [log] [tgz] |
---|---|---|
author | Daniel Norman <danielnorman@google.com> | Fri Mar 18 15:46:27 2022 -0700 |
committer | Daniel Norman <danielnorman@google.com> | Fri Apr 29 15:07:48 2022 -0700 |
tree | 9e6d890417844c3aa29fad252d967848dd897151 | |
parent | b27140daa032ecebf5bfceb816a27f80c3f4c020 [diff] |
Infers custom vendor partitions. Rather than hardcoding a list of allowed vendor partitions, we accept anything in the vendor target files that is not a framework partition. Also extend support for inferred misc_info keys when the device uses SYSTEM/product or SYSTEM/system_ext. Test: test --host releasetools_test Test: Use to merge a device with a custom IMAGES/*.img in the vendor build, and SYSTEM/system_ext in the system build. Bug: 225902565 Change-Id: I638c0f9c019357150516ea6c208ecd60c03c450f
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.