| commit | f031825560bc265469a359c0d5bf2e23a65da9dc | [log] [tgz] |
|---|---|---|
| author | Daniel Norman <danielnorman@google.com> | Mon Apr 15 11:34:56 2019 -0700 |
| committer | Daniel Norman <danielnorman@google.com> | Wed Apr 17 10:22:11 2019 -0700 |
| tree | 4f6e0a07ddea240120d96fe8a3938048965ae6b0 | |
| parent | fdb38817ea5784872b236e555874dc18234f72b8 [diff] |
Adds --output-super-empty flag to enable building super_empty.img. Any mixed build that uses dynamic partitions will require a super_empty.img image. This image must be created from the merged misc_info.txt file, so adding this functionality here simplifies the creation of this image for users (versus having to call build_super_image.py manually after calling merge_target_files.py). Bug: 129976345 Test: Ran merge_target_files.py on a dynamic partition enabled build using the new --output-super-empty flag. Change-Id: I73901f363d73c9fae1af1579faa2a908369dbbec
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.