commit | fb30407477fe9aadc440dc5779294b4443bb3e74 | [log] [tgz] |
---|---|---|
author | Treehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com> | Mon Apr 15 23:13:22 2024 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Apr 15 23:13:22 2024 +0000 |
tree | fa051e42144b74fd4472fbac8c65ec0efc26b5b9 | |
parent | 1dce401c1bfbedae8ebf5e98c0074a48bc8699e8 [diff] | |
parent | 8466afaa6d76070a7d39841c9c38a947b43c2348 [diff] |
Merge "Make output of MakeVbmeta consistent" into main am: 8b1e29ae7e am: 8466afaa6d Original change: https://android-review.googlesource.com/c/platform/build/+/3042632 Change-Id: Ic6a994cf5ab9c46fa6b045e4c6a300031192eee2 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.