| commit | ed5c7452ecee89030abdb7536ef91f8308c56d2f | [log] [tgz] |
|---|---|---|
| author | Justin Yun <justinyun@google.com> | Wed Jul 31 04:09:28 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Wed Jul 31 04:09:28 2019 -0700 |
| tree | 280a1166cf3b85e83dd7f43c4ab99d984da44c9d | |
| parent | 7c7387f16f41e91506a04ca901cc699c82589698 [diff] | |
| parent | 1c8599376d3e0d63ebf24370673ac2fe0183be41 [diff] |
[automerger skipped] Merge "Add product and system_ext partition for emulator" am: 1c8599376d -s ours am skip reason: change_id Ifa67bd6ad475ac5912e8f919c7a771c9958bd5c2 with SHA1 ff3d62d31d is in history Change-Id: Ia45f4df586aeea25da5aa2f3b16dd0bae3bf8525
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.