commit | 8c2ae4f6978eb33df432b952fa1832cb938e23c9 | [log] [tgz] |
---|---|---|
author | TreeHugger Robot <treehugger-gerrit@google.com> | Fri Jul 24 20:14:22 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jul 24 20:14:22 2020 +0000 |
tree | cb426de21b4a6cfb8c1e06eb74b2cfdcb2f40dc4 | |
parent | f63c028a07590192c7f4b854d5c207b287cd1a48 [diff] | |
parent | 40eaccde22e01a84f69ab473bb0dd080a9f2ca44 [diff] |
Merge "add android-mainline kernels to aosp_arm64 build" into rvc-dev-plus-aosp am: ac69af7fc0 am: 98d4f05bff am: 40eaccde22 Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/12226085 Change-Id: If2a66738db41fc07ea027fd420c151cd34744ac4
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.