| commit | 6e46cab3b8cba2fe6e0c78e3cfb6baca4110fd19 | [log] [tgz] |
|---|---|---|
| author | Sam Saccone <samccone@google.com> | Tue Jul 09 12:32:51 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Jul 09 12:32:51 2019 -0700 |
| tree | 928ea5b235d4b4c48678460f59cb12a69ba7e406 | |
| parent | 1cc4ebcd4eac2415cba0e3dcbd099f029b87e9ff [diff] | |
| parent | 7c1576597de2745778ab853fe137de642d6e8f6d [diff] |
Merge "this is the subject" am: 73155879c5 am: 9af03f4cd1 am: 7c1576597d Change-Id: I0197bc1e3017a0ffb817b0f0d0a6a7d41ac9b646
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.