commit | 53a0a19fef69767a59f91be33941a543961b384c | [log] [tgz] |
---|---|---|
author | Treehugger Robot <treehugger-gerrit@google.com> | Fri Nov 12 07:19:55 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Nov 12 07:19:55 2021 +0000 |
tree | 5d00cbdf7f19ab35030ac8d6e75ee0d58202e96a | |
parent | edce9368fdf99a83dacba8538d90cd9abc8534cd [diff] | |
parent | 173e8a3f907a93b149884b2c195bf6ec640a5403 [diff] |
Merge changes from topic "fsverity_digest" am: 866d824328 am: f90fb54430 am: 173e8a3f90 Original change: https://android-review.googlesource.com/c/platform/build/+/1855993 Change-Id: Ib335c84762c9d743b29d20502e24db6be5443585
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.