summaryrefslogtreecommitdiffstats
path: root/core/dpi_specific_apk.mk
Commit message (Collapse)AuthorAgeFilesLines
* Support dpi specific aapt flags.Ying Wang2015-01-291-1/+1
| | | | | | | | | | | | With this support, you can set dpi-specific aapt flags like: $(LOCAL_PACKAGE_NAME)_aapt_flags_hdpi := --version-code 100 \ --version-name "100 which will override the --version-code and --version-name set in the base apk's LOCAL_AAPT_FLAGS. Bug := 18388705 Change-Id: Ie79d7b1b6bbf7463bce51ddae04ba81384ec58dc
* Support to build dpi-specific apk variants.Ying Wang2014-12-021-0/+70
In unbundled apps_only build, in addition to the base apk, you can also build the dpi-specific apk variants, with: LOCAL_DPI_VARIANTS := <a list of dpi names> Previously user needs to include $(BUILD_PACKAGE) repeatedly with the same package definition except dpi flags. With this change, all the dpi-specific apk variants share the base apk's compiled Java code and only diverge at the point we add resources/assets to the apk. Also we set up variables/targets/rules in a way those dpi-specific apks appear to be independent apks to the users, for example, you can pass "AppName_<dpi_name>" to tapas, and AppName_<dpi_name>.apk lives in its own intermediate directory. Bug: 18388705 Change-Id: I2ba4972ea7d1f796352fab2407888f996781ae44