| commit | c6e9f75834bd9b7c8e86bb7cd0da2f4f8c551679 | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jan 17 00:31:00 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jan 17 00:31:00 2020 +0000 |
| tree | bd65329607819fa663ce585bc1133b3926870aca | |
| parent | b165bab09b10609255b2c56224d5e13522e6c6c7 [diff] | |
| parent | bc491a64a37eba3b975752f246ba18a59967eb7a [diff] |
Merge "Add strict module check to package-modules.mk" am: 951ae30d56 am: a9d2208cb1 am: bc491a64a3 Change-Id: I3b5f49f2dfd2d7078a757d1a4c4fd743c00b3128
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.