2e046e6c61
Previously: * If EMMA_INSTRUMENT_FRAMEWORK=true then jacocoagent was added to the ART_APEX_JARS which itself is added to PRODUCT_BOOT_JARS. * If EMMA_INSTRUMENT=true then it was added directly to the PRODUCT_BOOT_JARS. * If both were true then it was added in both places ending up on the bootclasspath twice. Bug: 185369704 Test: m EMMA_INSTRUMENT=true EMMA_INSTRUMENT_FRAMEWORK=true droid m droid Change-Id: Id1d4d1c98455cb2859ed5e4071a0cf14fb40eec4 |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
Android.bp | ||
buildspec.mk.default | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
envsetup.sh | ||
help.sh | ||
METADATA | ||
navbar.md | ||
OWNERS | ||
PREUPLOAD.cfg | ||
rbesetup.sh | ||
README.md | ||
tapasHelp.sh | ||
Usage.txt |
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.