commit | aa902718817fa1a62bd2149477bd0f4db3600368 | [log] [tgz] |
---|---|---|
author | Paul Scovanner <pscovanner@google.com> | Thu Mar 18 17:40:16 2021 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Thu Mar 18 23:59:31 2021 +0000 |
tree | 2606bebeebf4c20cc138420dc606bd618725f8b0 | |
parent | 3de8fdaeceb6d072271c5d5ce0cff1b77a0e8b98 [diff] |
Update Security String to 2021-05-05 resolve merge conflicts of 321db2f846e2f1d0f6a25cd0e16deb59dadf774d to rvc-qpr-dev Bug: 182937985 Change-Id: I248e89c967a3b02e072f477594a86b568d0f94a2 (cherry picked from commit 10e01bc86527689e4bc69ef7fb0d0077cf2844bf)
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.