| commit | 8f38240406b48bb226fb113dbe371300f5d23210 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Tue Jul 02 17:17:22 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Jul 02 17:17:22 2019 -0700 |
| tree | 1d86dce9d6e65ca6f1e3e1235f18a59a25299905 | |
| parent | d2ccc9bcabc50ba48222eda2c3747bbacca12bd0 [diff] | |
| parent | 22043a3cd291df3d683d0579b90b902556258b12 [diff] |
[automerger skipped] updatable_apex.mk is not inherited from mainline_system.mk am: 09dcc68663 am: e39ec1ecaf am: 22043a3cd2 -s ours am skip reason: change_id I3c4e1e4b2bbebd675904d148dd18acb57ecbdfe9 with SHA1 5fd45bbeb0 is in history Change-Id: I13c703714d9caebecb092a6c81521740d85e7dd0
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.