| commit | c30cc7d3432e5a3d701281a1c7364991a89e0d9c | [log] [tgz] |
|---|---|---|
| author | Adam Seaton <aseaton@google.com> | Wed Mar 14 00:38:23 2018 +0000 |
| committer | android-build-merger <android-build-merger@google.com> | Wed Mar 14 00:38:23 2018 +0000 |
| tree | 1204396c9edf4cc0da198255aca91c723c1a1b11 | |
| parent | 17444d16c2fbcd7e89f3a7a5a3cf1f634da37d67 [diff] | |
| parent | 47e4c774387182eb3cbddeb2d08d6d9fc2185df7 [diff] |
[automerger] [DO NOT MERGE] Updating security string for nyc-dev to 2018-05-01 bug: 74345861 am: 7c0f23dce5 am: 21f45f7edc am: 5a2c0096d5 am: bc62637ffa skipped: 262656a47f am: c3dd369446 am: 98086a211c am: 47e4c77438 -s ours Change-Id: I5b2bb6033ef974d93e5d092c5b50abc0babbfcf1
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.