| commit | 0665927c9cc9ae61120913f513ac5f51a472f606 | [log] [tgz] |
|---|---|---|
| author | Zach Riggle <riggle@google.com> | Tue Apr 03 15:19:44 2018 -0500 |
| committer | Dan Willemsen <dwillemsen@google.com> | Sat Nov 17 11:37:45 2018 -0800 |
| tree | 8384a2f57eb2c904b4e7b7be6ec661cecd1a5d6c | |
| parent | d04107683b2c23526d64226b00b8084d11099680 [diff] |
Add sanitizer-status to PRODUCT_PACKAGES_DEBUG This ensures all -userdebug builds have the sanitizer-status binary, which is used to check which build flags were used for a given image. It is important to distinguish between what the build fingerprint claims, and what is actually available on the phone. Change-Id: Iac1eabb8c5ed885a057f7a302b1887b7e9c4ccbc Merged-In: Iac1eabb8c5ed885a057f7a302b1887b7e9c4ccbc (cherry-picked from 3a26f80cd4461218f1417779809a6bf3211be002)
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.