| commit | f712ce79f5dbc49e0dda74f4fcc5c1bc9525f09c | [log] [tgz] |
|---|---|---|
| author | Jeongik Cha <jeongik@google.com> | Tue Jan 08 12:41:48 2019 +0900 |
| committer | Jeongik Cha <jeongik@google.com> | Wed Jan 16 14:27:21 2019 +0900 |
| tree | b32c36bcbcf567c487c6923166e9dedb58c58e13 | |
| parent | 371f557f8ef8d2bdc8c28aa408af895d6f7df787 [diff] |
Execute appcompat for apps built from soong Appcompat runs for app defined in Android.mk, but not in Android.bp So make appcompat run for app from soong(Android.bp) Bug: 110073830 Bug: 122026042 Test: m out/target/product/$(get_build_var TARGET_DEVICE)/appcompat.zip Change-Id: I73832410ec5850222b04086c2a377146886ba035
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.