aboutsummaryrefslogtreecommitdiffstats
path: root/build_test.bash
diff options
context:
space:
mode:
authorVishwath Mohan <vishwath@google.com>2018-05-28 13:54:48 -0700
committerVishwath Mohan <vishwath@google.com>2018-05-28 13:57:48 -0700
commit9ccbba0200cf56cc6b1b09bc45fa2efb1ea9a411 (patch)
treef50e38744fd892ff9b4469695f4bf6532784af68 /build_test.bash
parent1c54f66bd56d00592b6ce55826411ae6af9e2697 (diff)
downloadbuild_soong-9ccbba0200cf56cc6b1b09bc45fa2efb1ea9a411.tar.gz
build_soong-9ccbba0200cf56cc6b1b09bc45fa2efb1ea9a411.tar.bz2
build_soong-9ccbba0200cf56cc6b1b09bc45fa2efb1ea9a411.zip
Disable CFI for vendor variants of all components
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 (this CL), 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: I648edf13346b18fd88b623682e8590ed44709e0d
Diffstat (limited to 'build_test.bash')
0 files changed, 0 insertions, 0 deletions