| commit | 2bbb4d7478f933a229dcdd0a313a48c0ac34346b | [log] [tgz] |
|---|---|---|
| author | Kousik Kumar <kousikk@google.com> | Thu Oct 15 05:09:23 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Oct 15 05:09:23 2020 +0000 |
| tree | fe79faaeb58490802fb24314e58cf6edec4b8135 | |
| parent | 689bb8dece0e1375baf7ff8c95dc99966a27e922 [diff] | |
| parent | 3514f8d6e0b03a3f6263adad8c31766cea352b40 [diff] |
resolve merge conflicts of 602859b18603fea642cbcd486563f6bfa981eb4d to rvc-d1-dev am: 3d723c29d1 am: 7251bdc6ae am: 3514f8d6e0 Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/12735596 Change-Id: Ic3cae10fe555428b7b1f497936ab392de9d556e3
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.