| commit | fbe3709e2757df74f297106db01f788e9eb809c6 | [log] [tgz] |
|---|---|---|
| author | Bo Hu <bohu@google.com> | Fri May 01 23:42:07 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri May 01 23:42:07 2020 +0000 |
| tree | a732a608f35215bf27da765c5db14400470d4767 | |
| parent | 01a29d7f5e6b9bb58e9d00f65385776358681fab [diff] | |
| parent | 4d6f4f6c9ef8dc770cbf91483a859f4a3a097b43 [diff] |
[automerger skipped] emulator: enable vendor boot image am: 4d6f4f6c9e -s ours am skip reason: Change-Id I258b69bd0cdc4fb0a99b1a04567051e8d32c389a with SHA-1 8fd437c80a is in history Change-Id: I8fe3c4dd689d030e86c48528ababee9ab6ef4af4
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.