commit | fe67f1490695c3cbe5e2954d127255746e9c7c01 | [log] [tgz] |
---|---|---|
author | Roland Levillain <rpl@google.com> | Mon Oct 28 19:47:58 2019 +0000 |
committer | Roland Levillain <rpl@google.com> | Tue Oct 29 17:45:04 2019 +0000 |
tree | 50bf09894093fc99cb6d96759a7c7e8900afcb0c | |
parent | 5ec356acff6b57adf0980e8a32acf6cffb6e213c [diff] |
Remove module `jacocoagent` from `TARGET_CORE_JARS`. Before this change, `jacocoagent` was conditionally added to `TARGET_CORE_JARS`. However, this module is not really part of the Android Core Libraries (also, we plan to remove `TARGET_CORE_JARS` from `PRODUCT_PACKAGES`). Remove it from `TARGET_CORE_JARS` while keeping it in `PRODUCT_PACKAGES` and `PRODUCT_BOOT_JARS`, to keep having it installed and being part of the boot class path on devices (under the same conditions). Test: Check that: export EMMA_INSTRUMENT=true && unset EMMA_INSTRUMENT_STATIC && m installclean && m systemimage generates a system image that contains these files: /system/framework/apex-jacocoagent.vdex /system/framework/boot-jacocoagent.vdex /system/framework/jacocoagent.jar /system/framework/<arch>/apex-jacocoagent.art /system/framework/<arch>/apex-jacocoagent.oat /system/framework/<arch>/apex-jacocoagent.vdex /system/framework/<arch>/boot-jacocoagent.art /system/framework/<arch>/boot-jacocoagent.oat /system/framework/<arch>/boot-jacocoagent.vdex Test: Run test ATP test avd/avd_boot_health_check on build target cf_x86_phone-userdebug_coverage Bug: 143304991 Bug: 142944799 Change-Id: Ib047a394342aeffbfec26ebc756159f145d6523e
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.