commit | a9124c4b37ea1308b3b7c314befb232eb5e8432e | [log] [tgz] |
---|---|---|
author | Treehugger Robot <treehugger-gerrit@google.com> | Tue Oct 27 05:04:42 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Oct 27 05:04:42 2020 +0000 |
tree | e16d59f36f12e657cc838954f652a2ac332bdf27 | |
parent | e7943cfccf6fa24d5c8711f039ee11f55ddfe9de [diff] | |
parent | 1e92ac7f73d1ec2cd53b055071ec97d7aaa1c13b [diff] |
Merge "Cleanup references to system/core/liblog -> system/logging/liblog" am: 89dccb3cf9 am: 71d086d0ca am: efd9297362 am: 1e92ac7f73 Original change: https://android-review.googlesource.com/c/platform/build/+/1473818 Change-Id: I90d4b31576a123298ad055aaf0f030c0f931fb04
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.