| commit | 8938906fa60c0127cf5e9ef86b3eb04cf2d23c18 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Fri Jul 12 08:10:10 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Fri Jul 12 08:10:10 2019 -0700 |
| tree | f9b24fd51555c4abc89592a973dcb27a1a2947e8 | |
| parent | 044d3d8e5c6cf532315ff0de4eccf5291ede2d94 [diff] | |
| parent | 0f6c1d2b47e13203f19b7eeef8fb072da98a38c8 [diff] |
[automerger skipped] Merge "releasetools: Ignore nonexistent APEX overrides." am: d077c5b88e am: 0f6c1d2b47 -s ours am skip reason: change_id I2bad0f5c00753ed36ec5ae3431c7dc2ff1fc3e9c with SHA1 b369c7226a is in history Change-Id: Ia348c8e8555e2ada9f54a4a03a3e5ee1b338d91d
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.