| commit | 60beecc90ca5685a867eb06d6f73d2bac315ec55 | [log] [tgz] |
|---|---|---|
| author | Evgenii Stepanov <eugenis@google.com> | Fri Jan 18 13:53:52 2019 -0800 |
| committer | Evgenii Stepanov <eugenis@google.com> | Fri Jan 18 14:06:11 2019 -0800 |
| tree | 811986b463ef08d949534bf5ea163b7a7294ff3b | |
| parent | ab9de0ab6ef742d72d00369baf67852b8d67f3e8 [diff] |
Limit 2 uses of SANITIZE_TARGET to ASan. These two places are checking for ifdef(SANITIZE_TARGET) but what they are really looking for is the second stage of ASan build. Fix the checks so that they do not apply to HWASan. I have not seen any change in behavior, but there are some new files under /system in hwasan build that were not there before, and things keep working in general, so this feels like the right move. Bug: 112438058 Test: none; SANITIZE_TARGET=hwaddress keeps working Change-Id: I4544f408263b908be6ef4a47dd2b5c937e0c1f33
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.