commit | 6dd962fdda8eea1ef33544c00452f7a7352e93e5 | [log] [tgz] |
---|---|---|
author | yangbill <yangbill@google.com> | Wed Dec 08 15:30:23 2021 +0800 |
committer | Bill Yang <yangbill@google.com> | Tue Dec 14 05:54:30 2021 +0000 |
tree | 622d23815791dca55d67f69c1deeaf87abbc5a7f | |
parent | 0d8d378bd460ef369b03cda8c6f1fd619f4271e3 [diff] |
Preserve all COMPATIBILITY_SUITES values in module-info Extend COMPATIBILITY_SUITES in module-info to avoid overwriting previous values. In particular, this happens for the `host-unit-tests` suite which is automatically added by Soong rules only to be clobbered by the modules that have both device and host variants. Bug: 209806322 Test: source build/envsetup.sh ; lunch aosp_cf_x86_64_phone ; m out/target/product/vsoc_x86_64/module-info.json Change-Id: I56a2d4c9786ed3da1e788ba211ec1bcaa6559549
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.