| commit | 5382b3b206aae548914058e3b17a369f1e8d5856 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Thu Sep 03 17:57:18 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Sep 03 17:57:18 2020 +0000 |
| tree | c79f70f533e1bbd30b65623821c47b6fc4de6a66 | |
| parent | 0f3087ba84486025563d80326887423b5edb9a47 [diff] | |
| parent | b7c32f9021cc28f46b8986f12c525e916c63a7e1 [diff] |
Merge changes I3aa24904,I1f942dc0,If51d0f53,Ie27bdbd2 am: b9d0a2d4d5 am: b7c32f9021 Original change: https://android-review.googlesource.com/c/platform/build/+/1414178 Change-Id: I32d9076a43a8cdc46c2247e37666e35de8f4cf62
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.