| commit | 450197e2655785547f8a7b6bb9f327c7e21a6b53 | [log] [tgz] |
|---|---|---|
| author | Yike <yikezh@google.com> | Mon Sep 19 16:02:48 2022 +0800 |
| committer | Yike <yikezh@google.com> | Mon Sep 19 16:42:04 2022 +0800 |
| tree | 99273294a02de406b37f21042e6dcb985f32000d | |
| parent | 90195c958d317a6bd044d62be4a1c71b4f6e93cd [diff] |
Export the `target_required` property to module-info Some host test modules such as `python_test_host` use the `target_required` attribute to declare target dependencies that will be pushed to device. For example, `aidl_integration_test` references several target dependencies in the `target_required` attribute since those output files will be searched and pushed to device at runtime. Besides, those target dependencies can't be declared in the `data` attribute instead, since some modules' `data` attribute doesn't support multi-arch. So that, this information needs to present in module_info.json and exported to properly generate Bazel targets that include these dependencies. Test: m out/target/product/coral/module-info.json Bug: 222438068 Change-Id: Ia5ee103be1e7a811e1fdbd2b39252912b1a35c18
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.