commit | d8cde776070d0a2b592d5b53dac5c188b73a671b | [log] [tgz] |
---|---|---|
author | Inseob Kim <inseob@google.com> | Tue Nov 07 13:36:59 2023 +0900 |
committer | Inseob Kim <inseob@google.com> | Tue Nov 07 14:06:14 2023 +0900 |
tree | 9d0039a9e5a16dddaedad7c46a811d94d7c58dac | |
parent | 5f24ce615843c8ac4010bc3949ca8c4100ca83cd [diff] |
Add support for auto-generated characteristics RRO Setting use_rro_for_product will automatically generate an RRO package which contains resources with 'product="{PRODUCT_CHARACTERISTICS}"'. The RRO package will be installed to /product partition. The app will be compiled with '--product default', making the app identical to all targets. Motivation for this change is to minimize divergence of system.img. Bug: 294799593 Test: boot and idmap2 dump Change-Id: I549c2589c69eab7a1568510a7d1ff0c8a003f7ea
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.