commit | 5bf747710920d214b987aa78283015b2628b9d79 | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Wed Jun 17 07:08:20 2020 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Wed Jun 17 07:08:20 2020 +0000 |
tree | 02a04ad12d1964fc112bad0aebbab248f1963562 | |
parent | 79c422a0c2ca9f9682d0b4b96ba3dc7b9c7fc568 [diff] | |
parent | 875be1b2bb4191859d7ab5e7ccd08ca1c1bba3e4 [diff] |
Snap for 6598320 from 875be1b2bb4191859d7ab5e7ccd08ca1c1bba3e4 to mainline-release Change-Id: Ic1edf021662bff6b492ecf4a5d97bad44a38c95a
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.