commit | 5928936a3c50d3a194387f98d40e658ead3b8614 | [log] [tgz] |
---|---|---|
author | Owner Cleanup Bot <swarming-tasks@owners-cleanup-prod.google.com.iam.gserviceaccount.com> | Thu Nov 30 16:41:20 2023 +0000 |
committer | Owner Cleanup Bot <swarming-tasks@owners-cleanup-prod.google.com.iam.gserviceaccount.com> | Thu Nov 30 16:41:22 2023 +0000 |
tree | f2fa8393fde0d2852e2454de6a8ec0e19e75591b | |
parent | da0bc02bbfd8cb89140535e180048cb6e0487ead [diff] |
Remove lberki@google.com from OWNERS This suggested change is automatically generated based on group memberships and affiliations. If this change is unnecessary or in error, vote CR -1 and the bot will abandon it. Vote CR +1/2 to approve this change. See the owner's recent activity for context: https://android-review.googlesource.com/q/lberki@google.com To report an issue, file a bug in the Infra>Codereview component. Change-Id: Icd320d5ff1cf2bde24923f0f23d812e8299bd88d
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.