| commit | 1e9a0cd87db3239cad8cb52589fa303847ead2d7 | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Jan 13 02:39:37 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Jan 13 02:39:37 2020 +0000 |
| tree | ac1518e9161fcce37cd7d64cf2f1ecf6cf787a0e | |
| parent | 713c5dca91f3ceb14e642060fea0d42aa4212424 [diff] | |
| parent | 1d2de4f1bd1e5fa5aa7013fc6e01b5cbbbd6818e [diff] |
[automerger skipped] Merge "Correctly gather boot jars from APEXes" am: 7434764cce am: ad7f7a9eec am: 1d2de4f1bd -s ours am skip reason: Change-Id I6e255ce88c9bd80120b29197fb2637a64010f531 with SHA-1 bb0ec8c508 is in history Change-Id: I3c79254993fc8ed717d10d9d50cc2e85361242d8
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.