| commit | 37c0c7c82dd32e53bc4c5ee0a6d8acefb9294875 | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Tue Jul 24 17:45:08 2018 -0700 |
| committer | Yifan Hong <elsk@google.com> | Fri Jul 27 13:45:43 2018 -0700 |
| tree | d909d5232cb52cb38c93e1bdd76ac765b5f0f934 | |
| parent | ebc041af56757802c54daf18c04b27d7a153ae31 [diff] |
Build image for super partition ... for bootstrapping / initializing the device. Image is built to $(PRODUCT_OUT)/super.img when running `m dist`. For A/B devices, the image contains other partitions in the _a slot. Change-Id: I1459d62f02b95f142dfb3b7608f88ec6801dbf37 Fixes: 111758129 Test: m superimage -j
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.