commit | bee66d083ef7be16bd52e051b7a3fbb3907f3012 | [log] [tgz] |
---|---|---|
author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Sat Jan 25 01:16:14 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Sat Jan 25 01:16:14 2020 +0000 |
tree | 96caeb53242fc1007c1c7dc99b3e9634b7d4f81c | |
parent | 861dce8ccde05d4331cab9116ae3b7338626d9c3 [diff] | |
parent | 18201fab6f1dcc171feb28a7e1dd77b3e5ed177e [diff] |
Merge "Add BOARD_USES_RECOVERY_AS_BOOT to readonly list." am: 715c6a8794 am: 7bf299b6db am: 18201fab6f Change-Id: I299178abc7b52f451b7a3485507db43420dfa9fd
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.