commit | 2d01b662d646c83007131647c429934f73d31dd7 | [log] [tgz] |
---|---|---|
author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Feb 07 18:12:33 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Feb 07 18:12:33 2020 +0000 |
tree | c044b260066b50614ca3a8ab141bb96b51d71753 | |
parent | 5fdd1c77ece62d438c5b77cfc7d56aab28ed422f [diff] | |
parent | ffdfb16af442e057f7f1594eed69076a88ad5b67 [diff] |
[automerger skipped] Merge "Remove building WAPPushManager same as Q" am: 80eb043393 am: 5a7f8f1359 am: ffdfb16af4 -s ours am skip reason: Change-Id I3fa2664286222a5cecdb95fdff089a22e57b9f8c with SHA-1 80d723e7ff is in history Change-Id: I4f227b5b9aba942da99378a4a4c992c4a4893bcb
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.