| commit | f8d4dc57879f302b253268d61ec0e326d2d88a35 | [log] [tgz] |
|---|---|---|
| author | Vishwath Mohan <vishwath@google.com> | Mon May 28 13:38:24 2018 -0700 |
| committer | Vishwath Mohan <vishwath@google.com> | Mon May 28 13:51:05 2018 -0700 |
| tree | 68cf1cc250e148100f5219c11e16791e51882ed1 | |
| parent | 014d1fc9692aee8eecb95379452cc1dbe846c44b [diff] |
Apply CFI include paths to all product configs. The current VNDK ABI snapshot expects that CFI is disabled for components that either in the include paths (from cfi-common.mk) OR enabled directly in the makefile/blueprint. However, on non-arm64 architectures, the build system was only disabling CFI for vendor components in the include paths. This topic corrects it by (a) removing the include paths check to disable CFI for vendor variants, and (b) inheriting the CFI include paths in all product configs to ensure that when we update the ABI we're able to move to relying exclusively on (PRODUCT_)CFI_INCLUDE_PATHS. Bug: 66301104 Test: ABI matches for all architectures. Change-Id: I4d845cd9925354d565e06020c479cc3f7ab28f61
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.