commit | 608f4bf805e3ed89346be0f116337f3bac2c6dd8 | [log] [tgz] |
---|---|---|
author | Yi-yo Chiang <yochiang@google.com> | Thu Dec 09 06:21:54 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Dec 09 06:21:54 2021 +0000 |
tree | e7a15049ea7b09eb3d526280eda34d081e145d9d | |
parent | 48b1b7e6f0e7ad4e775d2a5fedad41423f2adf46 [diff] | |
parent | f02c28d8ab395cf166bc851927f05c0f1f7298b4 [diff] |
[automerger skipped] Merge "Roll-forward the VNDK snapshot list of GSI" am: f02c28d8ab -s ours am skip reason: Merged-In Ia9aab527d9c1fe1d1eb6c72ebc184a3fccad6a22 with SHA-1 33fc244de5 is already in history Original change: https://android-review.googlesource.com/c/platform/build/+/1913440 Change-Id: Id907c9a8e66ecffecb0fe044240e3d364c3876eb
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.