| commit | 22c1dd4e5695f8bf0268c0053564a350fdc339b0 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Tue Aug 06 11:22:14 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Aug 06 11:22:14 2019 -0700 |
| tree | e9d9dcfeb5a6d931359ed97abd023ac4a61c7655 | |
| parent | a602db0c9946cf1df512261b44013d7e490ec7b8 [diff] | |
| parent | ae8712c7c2298f67ed7108ecc0c7428cab536f4c [diff] |
Merge "releasetools: Don't write outputs if not in verbose mode." am: a514c4ec22 am: 3810585592 am: ae8712c7c2 Change-Id: I74fd0800bc98508734944c42df67c4b5e1b5f5c7
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.