| commit | 90cfe2876ce4b6e006ce8752f79dd5bbaf38b62c | [log] [tgz] |
|---|---|---|
| author | Joe Onorato <joeo@google.com> | Fri Feb 19 17:37:24 2021 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Feb 19 17:37:24 2021 +0000 |
| tree | c1894326397e3e6ff6d5ebac197bbcd39577c292 | |
| parent | a36d04850d71322f249f426bf580e0849da3d7f1 [diff] | |
| parent | 2fd88e0600fc9697e69ba4bd903cc0970b2f966f [diff] |
Merge changes I9c1995f8,Id6763781,I52e5c07f,I4706e32f,I7d74b226 am: 2fd88e0600 Original change: https://android-review.googlesource.com/c/platform/build/+/1580998 MUST ONLY BE SUBMITTED BY AUTOMERGER Change-Id: I2e87f06013df4e8e896426e603bbaa81c0763317
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.