commit | 519bd730061f8a7305d694f1803cda14d21cea4f | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Fri Apr 26 05:39:34 2019 +0000 |
committer | Jiyong Park <jiyong@google.com> | Fri Apr 26 05:43:22 2019 +0000 |
tree | f93f4b2c241a156d66b10843b789dfd43169b386 | |
parent | c5fc637c208e0bb059b7138422c22e7931f3a8d0 [diff] |
Revert "Temporarily not inheriting updatable_apex.mk" This reverts commit c5fc637c208e0bb059b7138422c22e7931f3a8d0. Reason for revert: all Pixels (except pixel 1) are ready to support updatable APEX Bug: 129035564 Test: run camera tests Change-Id: Ib01a97db857ad928d875d244dcd0b3cac8e080ee
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.