build: Fix QCOM_BSP_LEGACY cflags

Change-Id: I880f32892d9e082e3ba92878414f3cb3c6f08066
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
update LTO Linktime Optimization (MWisBest) (reverted from commit ff8a4f5fdd24ab4942a63afc4382e325b17ce1c6)
Revert : build: (Squash)Add chromium prebuilt support to envsetup.sh && The core Makefile

This adds a chromium_prebuilt function to envsetup.sh that is invoked by lunch to check
whether the chromium prebuilts are up-to-date or not. If not, it will be built from source
and then the new source built version will be pulled during brunch/mka bacon to become the
new prebuilts for future builds.

This is all opt-in through the USE_PREBUILT_CHROMIUM flag. Without it being set to 1,
none of this would be ran, and regular operations will go on.

PS13:
-use export TARGET_DEVICE
-replace git -C with params compatible to old git versions

(vendor repository for script)

Change-Id: I40f8c8dbd2a8a84a5c1b9f47ee04180a71ef4e07
(cherry picked from commit 84bbaf5a7426680b0b3723d11be852f756ed9e86)

Conflicts:
	core/Makefile

(cherry picked from commit a40bd82712e11e0f7f778972cb85514f135cd3bc) (reverted from commit 751a30f4703cfe62b2a3c5406bfd79165e2b2d0c)
build: update prebuilt chromium script

Prebuilt chromium: update for lollipop

Change-Id: I4e34feb26c1b4bec10fb751a10dbc52579d7cd07

Prebuilt chromium: Run a check for target device directory

this should fix the issue that arises if device fails and device is built again,
chromium will error out because it thinks the prebuilt files exist (which they are
not, directories are just created).

Signed-off-by: Ayysir <ayysir@aospal.com>
Change-Id: I595cab268e66c738ccae9900150b36d7f9626a6e
(cherry picked from commit 32dad2952a7c9c924e18ca97336bcaefdc45fe5c)

(cherry picked from commit 5d849825cb5313a2fe1775f88b15da41048f73e3) (reverted from commit ec7d3ecd584bd0aabcd1c3d74fb40fe53f602212)
move chromium to cmremix tools folder (reverted from commit f7b0a6e6e3226729719c67cdb01d478bf522fe41)
build: change style console output of prebuilt chromium

Change-Id: I2c390f3c64d614e181ebcad4e9711a93d9c55d44 (reverted from commit d1ca52c96c8309c7376fce0c7c890d4bc37e27c2)
set chromium prebuild path in cmremix vendor (reverted from commit 367a0f468d0ea6782d06ff1f4d46602ec5683abb)
build: Add chromium prebuilt support. Working version with lollipop (Thanks omnirom )

(cherry picked from commit c70b1ec27ca6514be13246044ad976b9564381ad)

(cherry picked from commit d14bf47ac3d269ad373d854efcdcf22a4f1d9d68)
build: change style console output of prebuilt chromium

Change-Id: I2c390f3c64d614e181ebcad4e9711a93d9c55d44

(cherry picked from commit 1a03f568a12846de1270629f99eb974aefa7f3f2)

(cherry picked from commit d311e402b2f4af0199e6da0c7dd7fc856d20e37c)
Prebuilt chromium: Run a check for target device directory

this should fix the issue that arises if device fails and device is built again, chromium will error out because it thinks the prebuilt files exist (which they are not, directories are just created).

Signed-off-by: Ayysir <ayysir@aospal.com>
Change-Id: I595cab268e66c738ccae9900150b36d7f9626a6e

(cherry picked from commit 78e44765cb6d43fc23d78debaafff85b40ae03c4)

(cherry picked from commit e202d002c6d38966f97fdf1b8726bc15ac1e2303)
Update chromium_prebuilt.sh for 5.0

Change-Id: Idfd9b28f048447bf69b0f1c710b0ee354eff829a

(cherry picked from commit ae9233f184e941111356ca2af2b8a008bf5ca581)

(cherry picked from commit 2c71355fb8b39f515f7bc94690755eb7197f88e0)
build: Fix PreBuilt Chromium refs

Change-Id: Icc553d5be1e71d8c754bc85b6906252e5690b508

(cherry picked from commit 18538dcae770f33f6a802cd17e238b7f030d69b3)

(cherry picked from commit 5f9a93b21d470fb2c7656e0d8b86f3ca87178cd4)
Prebuilt chromium: Run a check for target device directory

this should fix the issue that arises if device fails and device is built again, chromium will error out because it thinks the prebuilt files exist (which they are not, directories are just created).

Signed-off-by: Ayysir <ayysir@aospal.com>
Change-Id: I595cab268e66c738ccae9900150b36d7f9626a6e

(cherry picked from commit cabd388bc2e55c83fd4103d93ecf595adb54e479)

(cherry picked from commit e8cac21a04f751b5a75761f56bfb6ba820a531ee)
build: Add chromium prebuilt support to envsetup.sh && The core Makefile

This adds a chromium_prebuilt function to envsetup.sh that is invoked by lunch to check
whether the chromium prebuilts are up-to-date or not. If not, it will be built from source
and then the new source built version will be pulled during brunch/mka bacon to become the
new prebuilts for future builds.

This is all opt-in through the USE_PREBUILT_CHROMIUM flag. Without it being set to 1,
none of this would be ran, and regular operations will go on.

PS13:
-use export TARGET_DEVICE
-replace git -C with params compatible to old git versions

Conflicts:
	core/Makefile
	envsetup.sh

Change-Id: Ia040423e90abc2ef647717a41d9d972bd90ba780
(cherry picked from commit 552d536b2645c5b54fc49976105a51564fcff61b)

Conflicts:
	core/Makefile

(cherry picked from commit 650ddff8c3cd8f7b173dc68ce6d3c14119ab9c1b)

(cherry picked from commit 06242841b001d5d9acc1eb1226f3244035b8a37a)
derp fix
Merge remote-tracking branch 'CM/cm-12.0' into cm-12.0