commit | ee25b9642d87a098c78e97ed9ab46ff70db28d82 | [log] [tgz] |
---|---|---|
author | Yifan Hong <elsk@google.com> | Tue Nov 05 11:39:39 2019 -0800 |
committer | android-build-merger <android-build-merger@google.com> | Tue Nov 05 11:39:39 2019 -0800 |
tree | dcab94d0aecfbeaf8f4a9ede74bc9b12b259dcb8 | |
parent | fccbf585ad4f88319e18e88caf2dd7ef936baad6 [diff] | |
parent | 92d94de021bc9147ae8936a5bde658cc14745082 [diff] |
Merge "Support Factory OTA for Virtual A/B devices" am: f5ad6e5443 am: 5fb0960a73 am: 92d94de021 Change-Id: I8b242d083e8310091ad7523d81d2e110e6b0c4ab
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.