| commit | d31b2fd06876d2d1e77715f36dea2e045012732f | [log] [tgz] |
|---|---|---|
| author | David Anderson <dvander@google.com> | Tue Oct 08 12:49:05 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Oct 08 12:49:05 2019 -0700 |
| tree | 39b4e0cb382eada8618549d243a541a1d9671129 | |
| parent | bf9673a1248d774cbc29e4525562a64ae53836fe [diff] | |
| parent | a68c76d4ac1c47634cf22b4afcd96de2a23d4f96 [diff] |
[automerger skipped] Merge "Add IBootControl HAL 1.1." am: a8b633d181 am: 0c61e14227 am: c24146981a am: a68c76d4ac -s ours am skip reason: change_id If09d031e5acf1178fce942526782a41426c5180b with SHA1 fe1523d068 is in history Change-Id: I0d195e67a9fdc53100b56c15c4f588699f8fe764
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.