commit | 70b54f04dcde8a2cf09e511f527dc9c126579b08 | [log] [tgz] |
---|---|---|
author | Elisa Pascual Trevino <elisapascual@google.com> | Fri Jan 12 00:22:59 2018 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Fri Jan 12 00:22:59 2018 +0000 |
tree | ee67518183da18762d94f5b1fb262b5dd064728b | |
parent | c615ff3f020bf01fe101ce653c225e0bb3743b0a [diff] | |
parent | 74ba94d143bc8f3deb0696495d849cbfd8e96bf9 [diff] |
[DO NOT MERGE] Update security string to 2018-03-01 for mnc-dev Bug:71860241 am: fa4234e1df am: a615903311 am: 81e61008ed am: 51e7d3a175 -s ours am: cd6054fa86 am: 6619c472f3 am: a1c02ac99e am: 2daf3f586c am: ba60cad7ab -s ours am: 587ec653f1 am: fdac6439e4 am: 74ba94d143 Change-Id: Ic0c409b86b5bb5d304d8fa8946dde17575f5094e
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.