Fix QCOM_BSP_LEGACY

Checks in the Android.mk files do not enable the cflags for .h
files, causing a build that crashes constantly.

Change-Id: I315c760488445629fda860ba70066417c7d68b8b
build: Clean up QCOM flag definitions

Change-Id: I66bca2db83260ccd65b82e540ee9f7961f00b030
build: Add QCOM flags to Clang CFLAGS

Change-Id: I56f0d4106f5d3d27c1ace744d30c1c81f0052bbd
build: Remove unused qcom CFLAG

Change-Id: I6ead3e57899bcb007d4d284901f918a65a9e6926
recovery: set 18x32 on 560dpi as well

* this is the setting for shamu, it should be comparable to xxhdpi

Change-Id: I4d4b0405b6fcb3493dc5da0a712ce54f83d9ab6f
releasetools: clean up residual targetfiles-* dirs in /tmp/

Change-Id: I3792307663f8a85513e102c8bf3d78cf4e514760
build: Set QCOM global cflags for secondary arch

Change-Id: I637d94f9b0ddee2c8d6057de44355e482163dd36
build: Fix copypasta in 2nd target clang flags

Change-Id: Ieedce8754b145e53d72a5d6a4b41fbe5cdf6473f
build: Add changes to release tools and mkbootimg

Change the prototype of LoadRecoveryFstab to take in the device type
as a argument. Fix the case where mkbootimg was being passed a incorrect
argument.

Change-Id: Ic6ac596d8d96d3a5effbdf513763ec1cb92b1a03
build: Allow devices to specify a RIL variant

Change-Id: Ia5d35d916be358fb7be7ead6bd05cc3628b35a37
core: Get the RIL variant path into the global includes

 * Need to have this in the global path, so shuffle things around a little.

Change-Id: I2dd2b378d17ff3fa0e379793df31d68964d87278