| commit | fc41d361914f44a479c3f63aabb704f6e2f0047d | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jan 03 19:56:43 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jan 03 19:56:43 2020 +0000 |
| tree | 8eea6cc8ec43611ebdc6bde9acbf562a527a8cae | |
| parent | 882a93434e1d993ccef6c648598801718847026a [diff] | |
| parent | de4fd03ad9faf54467b4c77aa0ec17102370ff03 [diff] |
Merge "Add Soong android_app and android_test modules to javac-check" am: 6e54952b44 am: 253f31621e am: de4fd03ad9 Change-Id: Id4095e0d7dc27e0f01a8a1285d686bc17f8a5678
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.