| commit | 81c88ad58bd54a1a6b454293d113ecf278ff0184 | [log] [tgz] |
|---|---|---|
| author | Tianjie Xu <xunchang@google.com> | Wed Nov 07 11:36:19 2018 -0800 |
| committer | xunchang <xunchang@google.com> | Thu Dec 06 01:10:38 2018 -0800 |
| tree | 1715f11d817f7d3ee553aefab0ddb20dfba038bc | |
| parent | 696dd3bd9399b93eebefbe74cadcbdda7665cc9b [diff] |
Generate the recovery text images at build time We used to manually generate the background text images for recovery. That process requires opening various emulators and takes a long time. Now that the host Java tool is ready to generate these images, we can embed the generation step into the build of the recovery image. Since there's currently no make variable that defines screen width of the device, we put the commonly used values for pixels here, i.e. 1440 for xxxhdpi and 1080 for xxhdpi. Devices with other dpi can still use this feature if they define the screen width in their config files. Test: build bootimage with screen with set/unset Change-Id: Ic8389a527e6e7194de58a9c50763e841e886652b
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.