| commit | 593be3c494df9d40d45cb692f0e4a665f2fd884e | [log] [tgz] |
|---|---|---|
| author | Paul Scovanner <pscovanner@google.com> | Fri Apr 12 20:54:41 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Fri Apr 12 20:54:41 2019 -0700 |
| tree | 89a4f4669e5dd628f12fd561a501c17189d23f33 | |
| parent | ac3ae589d55ff025ad295d968a5a4baefcc53f5c [diff] | |
| parent | e90b407c2fd0f2a442ed9084594183479497ea46 [diff] |
Update Security String to 2019-06-05 Bug:129374896 Merged-In: 2c26c3d4c0314f8a3f905e5a7081556f7b4b353a am: 3ae4e858b7 am: cce67c52c9 am: e90b407c2f Change-Id: I451be3f8467540539c00be5d02798be830f89ff1
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.