commit | 3ab6aebc86eebc9c95736efff90bf4b62773a325 | [log] [tgz] |
---|---|---|
author | Paul Scovanner <[email protected]> | Mon Dec 14 23:24:33 2020 +0000 |
committer | Automerger Merge Worker <[email protected]> | Mon Dec 14 23:24:33 2020 +0000 |
tree | d274b60ae84e664434598afead16c9f0e3fa2e3e | |
parent | d4d46ab023a1baa3b10506d01e8137125d8d4075 [diff] | |
parent | ad55b25e81c410919084a110c74bb17251b98ae3 [diff] |
[automerger skipped] Update Security String to 2021-02-01 am: ad7b650e2d am: ffc4671fce am: e1b0fa94d3 am: ad55b25e81 -s ours am skip reason: Change-Id I6a1139d288c24a11289fc53c9022fd6d70acd8e6 with SHA-1 d4d46ab023 is in history Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/13219376 MUST ONLY BE SUBMITTED BY AUTOMERGER Change-Id: Ibceff73843f7106c5219786032454de44c414f41
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.