| commit | 5fb2de70868698c6e319e330046436113ff634ee | [log] [tgz] |
|---|---|---|
| author | Ivan Lozano <ivanlozano@google.com> | Wed Dec 12 10:04:34 2018 -0800 |
| committer | Ivan Lozano <ivanlozano@google.com> | Wed Dec 12 10:22:30 2018 -0800 |
| tree | a0275ca3672e4f61ecd0313b86ecb1c6705e6ce9 | |
| parent | 1e57a89bf9df4f10ce96dbac4f5a9a2349dde930 [diff] |
Add make var to avoid recovering with diagnostics. Add a LOCAL_SANITIZE_NO_RECOVER variable that allows specifying which sanitizers running in diagnostics mode shouldn't recover. This can help debugging as we test enabling sanitizers in new libraries since it'll cause tombstones to be generated along with the diagnostics information. Bug: 80195448 Bug: 110791537 Test: Compiled test module with this flag, checked compiler command. Test: Test module crashed, tombstone contained diagnostics information. Change-Id: I441b9c873e54bf6404325f4d0ac59835350c2889
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.