| commit | e508169caf2a9c6d83b5d758023ed1d8f3b5d03e | [log] [tgz] |
|---|---|---|
| author | Ivan Lozano <ivanlozano@google.com> | Fri May 11 14:09:36 2018 -0700 |
| committer | Ivan Lozano <ivanlozano@google.com> | Fri May 11 15:31:25 2018 -0700 |
| tree | 205842dc6ddd937dc75140c04630e0a5e2d6ed27 | |
| parent | d744f8cc8efc9967db222238ba330e90594b4445 [diff] |
Don't export UBSan minimal runtime symbols. When linking in the UBSan minimal runtime, don't export the symbols. This was resulting in an edge case where symbols were sometimes undefined at runtime on address sanitized builds if static library dependencies were integer overflow sanitized. Bug: 78766744 Test: readelf on libraries show either inclusion of the shared library or no undefined symbols related to the minimal runtime. Change-Id: I4382cc72baefd7fa96cd83e8349e82f7b083f5aa
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.