| commit | 2b6fdb3dabb70404d5f0f8919f52e2feb7c124c9 | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Dec 20 01:42:59 2019 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Dec 20 01:42:59 2019 +0000 |
| tree | f091815565058977fe7b1056f11ca0be9fac0806 | |
| parent | ff9ebf770562031bdc48f85d461785c9ecd1e567 [diff] | |
| parent | fc07c41a9e15b7ccab1e5fb305fe2714d94518cd [diff] |
Revert submission 1194828-revert-1191937-art_apex_available-DWXQGTKMAR am: f8b8c647e4 am: fc07c41a9e Change-Id: I87209392968251e9c7131be858fc1b580ee60e30
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.