| commit | 50196498d6f68a9dacee3d2cbaf6eff1d6e4eff1 | [log] [tgz] |
|---|---|---|
| author | Nikita Ioffe <ioffe@google.com> | Mon Oct 07 09:07:50 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Oct 07 09:07:50 2019 -0700 |
| tree | 55b433f5b01062df39a2454b76be3c3dc9edf2fc | |
| parent | 985ed05cf4ea260fab4f33932992d723ba085ac9 [diff] | |
| parent | 1faa3ffe94cce00fe8bcb19f78b9281ab5b3fe33 [diff] |
Merge "Unconditionally install shim apex on system partition" am: 42b2b54c2b am: e542a799c8 am: 1faa3ffe94 Change-Id: Ibc6b7e0f836ebd88d5aad8ba95014bcfec856910
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.