| commit | 838b580b4189fe9abc3a0ee50b9dd73f1e649387 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Sat May 02 11:06:55 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Sat May 02 11:06:55 2020 +0000 |
| tree | c497e28cd430de8d08e6ba482995748ac308747d | |
| parent | 41b588a75c7fea3febd39398f013e6eeca973bf0 [diff] | |
| parent | 8e679ce0647f01e5ec5b6df641033a9cf184e828 [diff] |
[automerger skipped] Merge "Stem names are used in apkcerts.txt" am: 6b872d794b am: 8e679ce064 -s ours am skip reason: Change-Id I56bc55e2231eb946617a9d6f97d55c9b61f3bff7 with SHA-1 f58fd52b14 is in history Change-Id: I520c7ee5c00882d031b0673e1c905701ddec6db5
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.