| commit | 6416a96bda29e5aacf0ae97a5a6b8efa3b3da8b0 | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Jan 07 23:18:26 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Jan 07 23:18:26 2020 +0000 |
| tree | a886034ec44d76dadd7008e804170f165db9f998 | |
| parent | 13fcfe37a2452eec1ec9e392cc6f73fb44a7b2e2 [diff] | |
| parent | 950604f8daa3cd723e3ac9b0dad680775a148221 [diff] |
[automerger skipped] Merge "vibrator: use package as name" am: c8b0187c8b am: e819518de8 am: 950604f8da -s ours am skip reason: Change-Id I382074d66b06669876d8f9fa4fc95b8a9c4dbf2a with SHA-1 a31e24a799 is in history Change-Id: I351e21c7557af9bf0bc8080af754f2458b5fd46d
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.