commit | cc4c5a7e2135a8b6ba5d9f04d807cf4ac12bd74f | [log] [tgz] |
---|---|---|
author | Elisa Pascual Trevino <elisapascual@google.com> | Fri Jan 12 01:25:34 2018 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Fri Jan 12 01:25:34 2018 +0000 |
tree | ee67518183da18762d94f5b1fb262b5dd064728b | |
parent | 70b54f04dcde8a2cf09e511f527dc9c126579b08 [diff] | |
parent | ab834f7d145b9000dd37b57c153710f896041d48 [diff] |
Merge "[DO NOT MERGE] Update security string to 2018-03-01 for nyc-dev Bug:71860241" into nyc-dev am: c3aee02b03 am: 4ab30bc502 am: f113fe294c am: 5a53ba3eb3 am: 82b90c8110 -s ours am: b75e95f40a am: 8d7856b98a am: ab834f7d14 Change-Id: I85dddc52cc7bced675fbe21728561e3622ea5dcc
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.