| commit | 1bd2a1d9462375d7d5d457caa5c7a1ee3db483af | [log] [tgz] |
|---|---|---|
| author | Daniel Norman <danielnorman@google.com> | Thu Apr 18 12:32:18 2019 -0700 |
| committer | Daniel Norman <danielnorman@google.com> | Thu Apr 18 16:37:29 2019 -0700 |
| tree | 53ba23b3e590d65dd7329a8198c38c695aad6ad2 | |
| parent | c1a836bab055496d21d0027cd6ff912c6dde2c7c [diff] |
Adds --output-img flag to enable building the IMG package. This simplifies the use case for mixed build users. Instead of having to remember to call img_from_target_files.py after this script, they can use this flag to automatically create the IMG package. Also includes an update to super_empty.img logic. The super_empty.img is now always created for dynamic-partition builds. The flag now only controls copying the super_empty.img to a user-provided location. Bug: 129976345 Test: Ran merge_target_files.py using --output-img and --output-super-empty and inspected the resulting img zip and super_empty.img. Change-Id: Ida602942bb7a6b4b94f4e225640af9104fc9360c
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.