| commit | dda64212464060cca427cd2cc5a1cb80840ff9c4 | [log] [tgz] |
|---|---|---|
| author | Sam Saccone <samccone@google.com> | Tue Jul 09 12:23:22 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Jul 09 12:23:22 2019 -0700 |
| tree | 5d753037e8bbdd3346808c31da72d8e856960ab9 | |
| parent | 7c1576597de2745778ab853fe137de642d6e8f6d [diff] | |
| parent | 66a46e28a663fe0d89ca963549d7112586318354 [diff] |
Merge "Revert "this is the subject"" am: cd7eb25a33 am: 66a46e28a6 Change-Id: Ia98a3bb78b6cb4c3a94f2d3cb8d0904f82fd99f4
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.