| commit | 91441ca650e79ee5e27425d23ae8b8a7450aea35 | [log] [tgz] |
|---|---|---|
| author | Paul Scovanner <pscovanner@google.com> | Tue Apr 09 15:44:39 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Apr 09 15:44:39 2019 -0700 |
| tree | 7cf6eabad38e5b8fc88bdd02eb17f727c0da2b2f | |
| parent | 0ad5c1fe8b76f92ca1f320a89debb1f9af47ede0 [diff] | |
| parent | ee14e56c76bf691461c8cc81c301cada0bc3abe4 [diff] |
[automerger skipped] [DO NOT MERGE] Update Security String to 2019-06-01 Bug:129374896 Merged-In:1f8f84de6133f82df8210fa9214475d7c5aaa2f0 am: 3e8a1393a7 am: 9231b34069 am: ee14e56c76 -s ours am skip reason: subject contains skip directive Change-Id: I270f4711add802057ccd3fe0327ca5691ea62a5a
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.