![]() The two components were mostly independant for a long time. Since I1e80a3f5e63d02b3859ecf74af21ca4c61f96874 the installation flow does not grant any permissions anymore and the last connection between these parts was broken. The new app "com.android.packageinstaller" in frameworks/base/packages/PackageInstaller will only handle (side load) package installtion and uninstallation. The exisiting app will be renamed to "com.android.permissioncontroller" and only handle permission granting and permission management. This change set also updates the make files to install the two apps on the appropriate devices. Test: Installed + uninstalled packages Change-Id: I37dda69218ea2a703a6379bb5bcbd3449b3360ad |
||
---|---|---|
core | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
Android.mk | ||
Changes.md | ||
CleanSpec.mk | ||
OWNERS | ||
README.md | ||
Usage.txt | ||
buildspec.mk.default | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
tapasHelp.sh |
README.md
Android Make Build System
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.