commit | 0b933424322c8c8fe745844e6223dbc82b76a4c0 | [log] [tgz] |
---|---|---|
author | Vincent Donnefort <vdonnefort@google.com> | Mon Feb 20 14:18:45 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Feb 20 14:18:45 2023 +0000 |
tree | df905806951bfd2f86d1772fe5c8ef9c38cf89a8 | |
parent | 222737c2cdf760ace0704f4d245021412e233723 [diff] | |
parent | 25ebc644b055913dc0eecd004c1b0b0869358f43 [diff] |
Merge "Fix missing dev nodes in init_boot.img ramdisk" am: 65af9993b3 am: 07738c42b2 am: f74012fd97 am: 25ebc644b0 Original change: https://android-review.googlesource.com/c/platform/build/+/2442241 Change-Id: I85900b7837f2d241b74d5ced8c05b59cefcf34c4 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.