| commit | 2e55115ab362dbff12002d694b51c164b476df46 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Wed May 17 10:56:44 2023 -0700 |
| committer | Colin Cross <ccross@android.com> | Wed May 17 11:01:19 2023 -0700 |
| tree | b3c8c6657ca59fef7fc35939758e8f5d32bbc3d6 | |
| parent | e4783d4b7a5e15f10e99a6042bd85010d3dd992a [diff] |
Don't build automatic RROs for tests Automatic RROs don't make sense for tests, the tests can't rely on overlays being installed on product or vendor. Creating the RROs causes a race during builds that build both droid and device-tests goals, as the RROs may be installed to the vendor directory as a dependency of the device-tests goal before or after the vendor image is packaged as a dependency of the droid goal. If the RROs are installed first and the vendor image is low on space it may result in an out-of-space error. Bug: 282885159 Test: Rule to build $OUT/vendor/overlay/SystemUITests__*__auto_generated_rro_vendor.apk no longer exists Ignore-AOSP-First: high priority build fix Change-Id: I760355ffb1818e91c02a98473312f9f21c149361
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.