| commit | 428cebcd7b837c2623440359978e68bb1ce9bc69 | [log] [tgz] |
|---|---|---|
| author | JP Sugarbroad <jpsugar@google.com> | Mon Sep 10 15:09:33 2018 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Sep 10 15:09:33 2018 -0700 |
| tree | 394ef6422a2ca5d157367eb3ee0fcca16ae482f7 | |
| parent | a113745d1f15a358f427e9997490099e34807377 [diff] | |
| parent | 839e8e56215caf59c12e7f7e81af0bb423d9af64 [diff] |
[automerger skipped] [automerger] [RESTRICT AUTOMERGE] Add new Android.mk to handle repo move am: fd72eaab91 am: 69d914c57b am: 5c6df3c9a2 am: cd5dfa01ed skipped: 428866c804 am: 58265f83b2 am: 422182a1ac am: 839e8e5621 -s ours Change-Id: Ib219842c69d669b83bcc8652e914425d5fe2fbec
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.