commit | 6a346010a058552b324feffcbba624fe6be5ac63 | [log] [tgz] |
---|---|---|
author | Luca Farsi <lucafarsi@google.com> | Tue Feb 11 00:57:53 2025 +0000 |
committer | Luca Farsi <lucafarsi@google.com> | Wed Mar 12 18:53:44 2025 +0000 |
tree | b14236ca0bfbb1954b25cb05724aa040751e4971 | |
parent | a8a2da75112bdde35ca68d0942e1bb989e212803 [diff] |
Keep track of which test infos use which target Modify build script to keep track of which test info uses which target, which will be necessary for intra-zip test discovery later Test: test Bug: 358215235 Change-Id: I3d51d6527396fc1538d51602ad84084dbcdc7b0e
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.