Gitiles
Code Review Sign In
review.shift-gmbh.com / SHIFTPHONES / android_build / b1b4e1e38b3a1d094de5515eaae2c7e6b6e542ed
commitb1b4e1e38b3a1d094de5515eaae2c7e6b6e542ed[log] [tgz]
authorPirama Arumuga Nainar <pirama@google.com>Fri Dec 10 15:26:16 2021 -0800
committerPirama Arumuga Nainar <pirama@google.com>Fri Dec 10 15:29:37 2021 -0800
tree07f5778e4c812d1ea5e9ba1f45e363b7fd2a355a
parent598cbbcde724845c16363c9f2e55e6f6f35da894 [diff]
Set a BIONIC_COVERAGE .mk variable

Bug: http://b/194128476
Bug: http://b/210012154

Set BIONIC_COVERAGE to true if coverage instrumentation is enabled for
bionic/libc.  This is used in system/core/rootdir/Android.mk to set
the default LLVM_PROFILE_FILE environment.

Test: Run tests with this topic and verify coverage still works and also
test memory-mapped coverage (death tests, JNI code in CTS)

Change-Id: I585f3e43dfcb82dd3c211051d354dd79ee77b1fb
1 file changed
tree: 07f5778e4c812d1ea5e9ba1f45e363b7fd2a355a
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. Android.bp
  9. banchanHelp.sh
  10. buildspec.mk.default
  11. Changes.md
  12. CleanSpec.mk
  13. Deprecation.md
  14. envsetup.sh
  15. help.sh
  16. METADATA
  17. navbar.md
  18. OWNERS
  19. PREUPLOAD.cfg
  20. rbesetup.sh
  21. README.md
  22. tapasHelp.sh
  23. Usage.txt
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.