| commit | 330af541eb4d2eea06af03f5a1b59717b0565c86 | [log] [tgz] |
|---|---|---|
| author | easoncylee <easoncylee@google.com> | Mon Mar 22 16:30:17 2021 +0800 |
| committer | Chun-Yi Lee <easoncylee@google.com> | Mon Mar 22 10:33:36 2021 +0000 |
| tree | 8be1f2ed907af030546f032b2ca33aebd53a810d | |
| parent | 680a64264562459001e316c33ed2ddfee9c427aa [diff] |
Build module-info.json in dist This is needed for test mapping to have module-info.json built out for device targets so that test harness can do some checks to ensure the test is properly configured in TEST_MAPPING files. module-info has alreay depended on droidcore, which will be built out in the infrastructure. Verified in a forrest run: https://android-build.googleplex.com/builds/forrest/run/L81000000840964024 Bug: 154931418 Test: m -j droidcore m -j module-info Change-Id: I76b97debe3fbd51c2dc033c91ed9c2eb73cfa8a2
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.