| commit | e4a549195cb75f24bb89742a1cc46967dc887dee | [log] [tgz] |
|---|---|---|
| author | Yike <yikezh@google.com> | Mon Jun 27 16:43:23 2022 +0800 |
| committer | Yike <yikezh@google.com> | Tue Jun 28 10:10:35 2022 +0800 |
| tree | d8802c1d61d55391240fd58ef74bb4dfe90e6588 | |
| parent | 836d78413a7eb0104c3d0d39893841366a10c16b [diff] |
Export the `host_required` property to module-info Some test modules such as `android_test` use the `host_required` attribute to include additional harness dependencies. For example, `CtsLibcoreTestCases` references `cts-dalvik-host-test-runner` in the `host_required` attribute since those jars are required by Tradefed at runtime. This information needs to present in module_info.json and exported to properly generate Bazel targets that include these runtime dependencies. Test: m out/target/product/coral/module-info.json Bug: 220991354 Change-Id: I8d2ab0da04c9f4aff17d290999c69ffe0534729f
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.