| commit | f03a265786a9e8a4fc6b843f38aded7b586563e3 | [log] [tgz] |
|---|---|---|
| author | Vishwath Mohan <vishwath@google.com> | Wed Mar 28 19:23:01 2018 -0700 |
| committer | Vishwath Mohan <vishwath@google.com> | Thu Mar 29 13:07:10 2018 -0700 |
| tree | d15f9a9275330851fa9ad4a9241929c287c2628a | |
| parent | df2a21794cd6bde432e7142fd5c7c3bbb5021398 [diff] |
Change PRODUCT_CFI_INCLUDE_PATHS to opt-out (Make) This CL changes PRODUCT_CFI_INCLUDE_PATHS to be included in all product configs by default. To maintain the status quo, the sanitizer logic has been modified to only respect this product config for Arm64 devices (where this was previously enabled). Bug: 63926619 Test: m -j60 # the device still has CFI enabled thanks to the default opt-in Change-Id: I22788d92be881d3290568488f5458c85e02ee8c7
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.