| commit | b71c33fbdcd9a6c6d602c38339e5164259c30f88 | [log] [tgz] |
|---|---|---|
| author | Sharif Elcott <selcott@google.com> | Fri Jul 20 16:09:43 2018 +0900 |
| committer | Sharif Elcott <selcott@google.com> | Fri Jul 20 16:10:51 2018 +0900 |
| tree | 105f80ed9a4e3a02090077fe32e67c1ed84fd138 | |
| parent | 3e583e0b3dc54e9fa58ca6ceb29713191bac5de1 [diff] |
Added Address Sanitizer clang config for x86_64. Without this, binaries built for an x64 target with Address Sanitizer enabled fail to execute at runtime, failing with the error message "No such file or directory". Test: 1) Build any Android target that has asan enabled, such as statsd, on any lunch target with suffix "_x86_64-eng". 2) Run 'file' on the generated executable. 3) You should see "interpreter /system/bin/linker_asan64" rather than "interpreter --gc-sections" Bug: 111667639 Change-Id: I5d7e7f307d954d4cd48ff88a7d9d6a5732276296
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.