| commit | c8d69fbdbac639752809aa46bab19da3d934f748 | [log] [tgz] |
|---|---|---|
| author | Ian Pedowitz <ijpedowitz@google.com> | Mon Mar 30 02:58:10 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Mar 30 02:58:10 2020 +0000 |
| tree | 0e578a78de7e72d47a0efe0908f86a5934746e64 | |
| parent | 3345835c808bcfed4076120f725263620fecee04 [diff] | |
| parent | d71e6ef694c9458e5906043a0169c8ce650b87cc [diff] |
RESTRICT AUTOMERGE: rvc-dev is BUILD_ID=RVC am: d71e6ef694 Change-Id: Ibbdb0689b786a3b9f0b8cb2bd532c994bf9cd4b4
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.