commit | 78d61e203aaddd062f36265a6ebea9b4c4f5557d | [log] [tgz] |
---|---|---|
author | Paul Scovanner <pscovanner@google.com> | Fri Apr 12 11:35:12 2019 -0700 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Wed Apr 17 08:16:51 2019 +0000 |
tree | ca72d7073f0652c83118bc2ec6f146ede87c7ffc | |
parent | 3ced66d63958fe58a4277ea4bd3e23224dc1552f [diff] |
Update Security String to 2019-06-05 Bug:129374896 Change-Id: I82bf91c0947fdc45db025a8fc0c069f718c7e1c3 Merged-In: 2c26c3d4c0314f8a3f905e5a7081556f7b4b353a (cherry picked from commit 603c06a1401f19da270b2425b4402779568a4cba)
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.