| commit | 665ba5366c575bb6f3e28a6e43370beaaba01e94 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Sat Apr 20 12:31:34 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Sat Apr 20 12:31:34 2019 -0700 |
| tree | 7992bcc30f61a393852e468488c4a0c75093d4a5 | |
| parent | ef78016dc26689554b451f118a3084e78a048209 [diff] | |
| parent | 97548ef31b07baa43baa6916233492ba6d2c03c8 [diff] |
[automerger skipped] Fix typo of PRODUCT_BUILD_ODM_IMAGE am: 97548ef31b -s ours am skip reason: change_id Ibe6523ca77aeb1ff6fdd138dcf2bfa46bcdeee59 with SHA1 25a6937d34 is in history Change-Id: Id7951cef0d78294bde854c88be7000276dcb291a
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.