commit | 6a5e9a21efa9da7033a4ed2ee6479d1c82f5752a | [log] [tgz] |
---|---|---|
author | Jeongik Cha <jeongik@google.com> | Tue Aug 20 19:24:43 2019 +0900 |
committer | Jeongik Cha <jeongik@google.com> | Tue Aug 20 19:24:43 2019 +0900 |
tree | 75d3b8522563cc126d9d33b361123900fb17a0ab | |
parent | f51a70b009b3557b173e804f0da377f2aa5417c9 [diff] |
SYSTEM_EXT supports executables Because TARGET_OUT_SYSTEM_EXT_EXECUTABLES have been omitted, we cannot install any executables in system_ext. So fix it. Test: set system_ext_specific true in some executable, and then check if it is installed in /system_ext/bin Bug: 139719550 Change-Id: I1bc7a2e6a7c25ec4b5b1ea6358ba8d3e1ae6331b
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.