| commit | 264e119cba15be43466a3214cc0d352fc5734747 | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jan 10 15:15:55 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jan 10 15:15:55 2020 +0000 |
| tree | 3e664663adfb3d1736f0b0b5f674947c61313787 | |
| parent | 8adf661c14005ada46cdc1c401e27bd119340cae [diff] | |
| parent | 5f8c93c7a29e1491275cf0aeb045f150569396a4 [diff] |
Merge "Use our prebuilt M4 for flex and bison" am: 5ec7b56e5d am: 5f8c93c7a2 Change-Id: Iaa0611529b0e49934e3c699702803cce8a02adb8
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.