| commit | 5b21b79d826e34f4e6a81985f4116593cd10475a | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Thu Apr 30 11:26:13 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Apr 30 11:26:13 2020 +0000 |
| tree | 3d860ae21df84c03ba57618f57e49aab4264538f | |
| parent | 4eea7b0ef73d593f6d79a8293c638f17814a113f [diff] | |
| parent | d4e85a97e75242e7465a8adbafac0b9a4dbe0ec1 [diff] |
Merge "Revert "remove emulator_vendor.mk from aosp_arm64.mk"" am: d4e85a97e7 Change-Id: I1576436f768348dffe64b4864fea69e590aa8ac7
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.