| commit | 01475b41fbac6755a269d13e5ba9261acdecab1d | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Thu Mar 23 20:37:34 2023 -0700 |
| committer | Colin Cross <ccross@android.com> | Fri Mar 24 04:33:07 2023 +0000 |
| tree | 513dd8dd61ac0bce3ad9e94513b54a2a44c9dd12 | |
| parent | 539fbc287e64fa761c84ba31e7deee965c2fe9d6 [diff] |
Don't read test mapping list in Make Reading the test mapping list in Make causes Kati to regenerate any time a TEST_MAPPING file is added or removed. Pass the file to the rule and read it during ninja instead. Bug: 274987114 Test: m test_mapping Change-Id: I68a76646d70c85b2cb992e4da52a7854acd370b9
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.