| commit | 7c9a9cb285fd376b2fbd61ae9bff67ff25363d8e | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Tue Aug 06 20:31:55 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Aug 06 20:31:55 2019 -0700 |
| tree | 7f0272ffb0e4c1a2ce19f0da48ee9def50aba640 | |
| parent | 5c138ab1b76ea1c2b22fe04cc13ff08b1d8036e6 [diff] | |
| parent | 3cd04a7abd797c3aa3d91ecf3ca916cedab4dac5 [diff] |
Merge "releasetools: merge_target_files sets verbose in main." am: 3738f37e22 am: 7552bbdfb6 am: d08461c861 am: 3cd04a7abd Change-Id: I97444dc74d02feb10695765ae8614ebb1b46d130
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.