| commit | 3e45e5f4d94bf6e7fee721ec90b46bf8909e2777 | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Feb 11 00:08:22 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Feb 11 00:08:22 2020 +0000 |
| tree | 0c62a139d19d2a2e8aaca146bf91575c7ced8a0e | |
| parent | 98bc85f9f9c426892183a0fc7dc587962b9a9f67 [diff] | |
| parent | 823e8030a82ea700dc9eb0a81dfb656545ee8ed9 [diff] |
Merge "Implement vendor snapshot" am: 7decc032c2 am: 823e8030a8 Change-Id: I877442e69f3d27a33dff1e8f8588a98bec9c0ec0
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.