| commit | c2ad5aac246814b3dba7b3d57ed19465b2e376b9 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Tue Jul 02 17:55:57 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Jul 02 17:55:57 2019 -0700 |
| tree | 1d86dce9d6e65ca6f1e3e1235f18a59a25299905 | |
| parent | 8f38240406b48bb226fb113dbe371300f5d23210 [diff] | |
| parent | e82022e35eb649eb04623542ed7dc51df29b0d7b [diff] |
[automerger skipped] Revert "Make mainline device use apex" am: 7d5dbf2be0 am: e4f48a9440 am: e82022e35e -s ours am skip reason: change_id I5cbaa767900d17039e8113f29b40d61c977764dc with SHA1 1cb902e510 is in history Change-Id: Iaabd91c80bf3becd942bfec432ed1439f9dd6af6
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.