| commit | bcc9fdc35cbda095272593ef9c95c284739d8ed7 | [log] [tgz] |
|---|---|---|
| author | Daniel Norman <danielnorman@google.com> | Fri Jun 14 15:58:34 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Fri Jun 14 15:58:34 2019 -0700 |
| tree | 7a30e21d50a7cdd2eb89e4c7fcd3fd7b320e316e | |
| parent | b9df5d139be2f5b7528554e7fda41bebba1947e8 [diff] | |
| parent | fb75669939118ec3e0f2e32f36fb40ffd4ea925d [diff] |
Merge "Allows skipping building the super images for partial builds." am: 87ebb3013f am: d3576727ea am: c7c103514f am: fb75669939 Change-Id: I2d9dbfc9c42dbf76610f74f5a4539c9270498f06
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.