| commit | 9a63c2a1ce89c5decc9c7adbc328046e4c76bc44 | [log] [tgz] |
|---|---|---|
| author | Steven Moreland <smoreland@google.com> | Fri Oct 11 14:15:07 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Fri Oct 11 14:15:07 2019 -0700 |
| tree | f913e6231e1e9a5cfa5592df437198aa68efe272 | |
| parent | f9e07d6b9bd19b52df0473702d290e007d40d3e5 [diff] | |
| parent | c58858de4c5de8c6fb9144b8f53a9b31a7db33d0 [diff] |
[automerger skipped] Merge "mainline_system: libhwbinder/libhidltransport" am: 2ce54fa76a am: a84540e557 am: 3b9d2dc689 am: c58858de4c -s ours am skip reason: change_id Ia142f8e67c31f66f86386b65e009d4faee502c11 with SHA1 3dbd647da5 is in history Change-Id: I6f8a20a23dc1df0dafd104d7fe0a08486879f7ec
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.