commit | 68e1289626629cc684a3796aaf4d2fa9ea25f718 | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Mon Apr 30 16:01:33 2018 -0700 |
committer | Jackal Guo <jackalguo@google.com> | Wed May 09 06:38:28 2018 +0000 |
tree | f24fa8c972ad07049a42b389462faa207538956d | |
parent | b17f384dd74f42f68ae1f20091fdb67cce1dc0d7 [diff] |
Allow PRODUCT_COPY_FILES to copy raw APKs into system_other Files in this partition aren't actually installed, so we don't need to use the BUILD_PREBUILT logic for APKs. Bug: 66960479 Test: try PRODUCT_COPY_FILES of an apk into system, errors Test: try PRODUCT_COPY_FILES of an apk into system_other, accepted Change-Id: Ie721d2b884c6badfbe0e46f55c265b770bed618b Merged-In: Ie721d2b884c6badfbe0e46f55c265b770bed618b (cherry picked from commit 7d957c911a47c7c4b98dfe6bf85d5ebbbb0ab62d)
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.