commit | 1c3cd37337733298a1ad18740bd714e007f35912 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Wed Oct 03 14:08:09 2018 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Wed Oct 03 14:08:09 2018 -0700 |
tree | 8cc6e0d42a1f7efd43f20b7149b6b0a2a63e2a07 | |
parent | 8478f1242788839c8a895d0aca3b21f711a2a88f [diff] | |
parent | 9ae934f9d9f7965451582d5b2a7e3e611a63b788 [diff] |
Merge "releasetools: Raise on image building errors." am: fabb2c9792 am: db6450a6e4 am: 9ae934f9d9 Change-Id: Iaf077042013cc19026901486547bc722824e8c02
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.