commit | e1e829efe139f56113cc2d2c98309daddfb0329f | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Wed Aug 29 20:36:00 2018 -0700 |
committer | Tao Bao <tbao@google.com> | Wed Aug 29 22:08:37 2018 -0700 |
tree | 86bba781427f1313599cd98acf9781dd656942f8 | |
parent | acdaa8fbacc6338e7e1aa3a0edd0feaa9d9e8b57 [diff] |
Map numeric dpi value to density bucket for recovery resources. When choosing the density for recovery resources, the code used to handle primary density values only, i.e. mdpi, hdpi, xhdpi, 400dpi, xxhdpi, 560dpi and xxxhdpi. Unlisted values, such as 500dpi, will be categorized as xhdpi, but with tiny font size selected for recovery. This CL improves the handling of numeric dpi values. It allows targets using numeric values in PRODUCT_AAPT_PREF_CONFIG, and maps that to a proper density bucket. Targets can still specify the density bucket directly, which will take priority. Bug: 111559919 Test: `m -j bootimage` with marlin/sailfish/walleye/taimen respectively. Check the chosen density bucket for recovery resources (xxxhdpi/xxhdpi/xxhdpi/xxxhdpi). Test: Set PRODUCT_AAPT_PREF_CONFIG to 279/280/281/500/559/560/640. Check the computed bucket and the selected recovery font file. Change-Id: Ia40fcdec5a2752c08172716bcc622a36a2a83cea
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.