558cb6c5ac
Since Make does not visit modules in topological order of their <uses-library> dependencies, information from dependencies to the dexpreopted module has to be passed via dexpreopt.config files. A build rule for a dexpreopt.config file depends on dexpreopt.config files for <uses-library> dependencies, and dex_preopt_config_merger.py script extracts the necessary information from dependency configs and patches the module's config. Bug: 132357300 Test: lunch aosp_cf_x86_phone-userdebug && m Change-Id: Id0b71170a4d2ab1d33059de0e9ad9d7e61f2345e |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
OWNERS | ||
README.md | ||
Usage.txt | ||
buildspec.mk.default | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
rbesetup.sh | ||
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.