| commit | 0aecdac89e83ffbe38e11ccb1fa057d07854b05f | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Wed Aug 05 17:06:34 2020 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Wed Aug 05 20:23:24 2020 -0700 |
| tree | 15c8932e51d1aed3c115165f435d83bb4a4f1081 | |
| parent | 48825727f68d4b9b197851e505a86f43a028cfbc [diff] |
Don't use the remote pool when using clang-tidy In Make, clang-tidy and clang run in the same action, but only clang can be remoted via RBE/GOMA. So to prevent running up to 500 clang-tidy instances at the same time and overloading the machine, use the local pool when using clang-tidy. This does limit the parallelism of the clang actions attached to clang-tidy, but hopefully that's not that much of a problem. Clang-tidy isn't enabled by default (opt-in per-build / per-module), and Soong does not run into this problem. Bug: 162615762 Test: m WITH_TIDY=1 nothing; build-aosp_flame.ninja is identical before/after Test: use_rbe m WITH_TIDY=1; inspect build-aosp_flame.ninja, see local_pool Change-Id: I7dd196fcf4183d175b9608d3d48cdcdf81b514ce
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.