commit | b9c27853fd3b4b8cf861fe36146fb5518c843939 | [log] [tgz] |
---|---|---|
author | Liz Kammer <eakammer@google.com> | Wed Jan 31 15:22:37 2024 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jan 31 15:22:37 2024 +0000 |
tree | 32a78cb17d76b770d347e628a9ec9a136a3a9a8f | |
parent | 73752e933c918323acb34965a28296a25779f96c [diff] | |
parent | 898efbfb7826d80452d9e749d3a6075b71f6853a [diff] |
Merge "Update benchmarks to handle cog workflows" into main am: 898efbfb78 Original change: https://android-review.googlesource.com/c/platform/build/+/2933372 Change-Id: Ic5a96fb6fb3e1270075e38a6250e724e9b448089 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.