commit | bd5e87d2342f81c8f0a432e142e1489dd79e7e07 | [log] [tgz] |
---|---|---|
author | Hongguang Chen <hgchen@google.com> | Thu Nov 17 07:19:37 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Nov 17 07:19:37 2022 +0000 |
tree | 177fde7387268b8260701df6a82a9e93aa819585 | |
parent | a43b4c49cb4e06c372565e9e55f92b81e14aae41 [diff] | |
parent | 425f7d1cb3fc5c1adc740db546c5b18227ea3c82 [diff] |
Support chained init_boot partition signing am: 425f7d1cb3 Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/20486714 Change-Id: Ic81c0d6e149ca185c62c3173480275719cd5df85 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.