| commit | b2219c7052353612c3151e969d810a696d549e84 | [log] [tgz] |
|---|---|---|
| author | yangbill <yangbill@google.com> | Fri Feb 18 15:27:53 2022 +0800 |
| committer | Bill Yang <yangbill@google.com> | Fri Feb 25 01:28:51 2022 +0000 |
| tree | e2e257f94785e4696b852f92ba07986baa2be4c4 | |
| parent | 3f852994b489372f8ce22bfe011e21241f85a1dc [diff] |
Add supported variants to module-info Export the list of variants (host, host_cross, device) a build module supports to module-info for downstream tools. The values correspond to the Soong `host_supported`, `host_cross_supported`, and `device_supported` attribute values. Bug: 220263783 Test: m out/target/product/vsoc_x86_64/module-info.json Change-Id: I10ae6ea21791d0d100686dcabecbce543a9adc3f
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.