commit | a2734a4d3280615fa09fa31a8e7a65acf65a644b | [log] [tgz] |
---|---|---|
author | Kousik Kumar <[email protected]> | Tue Nov 10 23:54:24 2020 +0000 |
committer | Kousik Kumar <[email protected]> | Wed Nov 11 11:31:04 2020 -0500 |
tree | 081bf0ad39eb54303aafd91e9965fae51b37ed44 | |
parent | 78c70d6abcdf7534918681e38a593b14a5403026 [diff] | |
parent | 602859b18603fea642cbcd486563f6bfa981eb4d [diff] |
resolve merge conflicts of 602859b18603fea642cbcd486563f6bfa981eb4d to mainline-prod Change-Id: Ic708c79073c7367162dd8e683ac9759f75778233 Merged-In: I988381f4f72061f7c6eb99d58593f92cfd618b1b
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.