Google Git
Sign in
android / platform / build / a52b6e9ba85ef65b90a8673180a686ee89f2026c
commita52b6e9ba85ef65b90a8673180a686ee89f2026c[log] [tgz]
authorJiyong Park <jiyong@google.com>Wed Sep 12 10:03:37 2018 +0900
committerJiyong Park <jiyong@google.com>Wed Sep 12 10:05:58 2018 +0900
tree7a72785459196658cd8995fa90cf73f0c2feec5d
parentd9a58852bd5b97d566a9ea59b343c0a86ad7024d [diff]
fix: linktype for recovery modules in ASAN build is native:platform

When ASAN is on, recovery modules are instaled to
$(OUT_DIR)/target/product/.../data/asan/recovery/root. However, since
this is not under $(TARGET_RECOVERY_OUT), their linktype is incorrectly
determined as native:platform, instead of native:recovery.

To fix this, use get_non_asan_path to have consistent paths when
determining the linktype.

Bug: 115361480
Test: m -j; SANITIZE_TARGET=address m -j

Change-Id: I75edb1fe193d8a1a8099d4f5cf498910ca868d38
1 file changed
tree: 7a72785459196658cd8995fa90cf73f0c2feec5d
  1. core/
  2. target/
  3. tests/
  4. tools/
  5. .gitignore
  6. Android.mk
  7. buildspec.mk.default
  8. Changes.md
  9. CleanSpec.mk
  10. envsetup.sh
  11. help.sh
  12. navbar.md
  13. OWNERS
  14. README.md
  15. tapasHelp.sh
  16. 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.