Merge "Add graphite flags" into lollipop
Add graphite flags

Change-Id: I482279c0b9448cb05d56ce183affa30a4ac7bd4f
Signed-off-by: Paul Beeler <pbeeler80@gmail.com>
Signed-off-by: Chet Kener <Cl3Kener@gmail.com>
LIQUIFY OPTIMIZATIONS V1

* This is an introduction of a BoardConfig.mk flag that will allow for us to LIQUIFY or Optimize builds like crazy.

This includes:

* Clang Optimized with -O3 Optimization
* Linker Optimizations
* Makes use of Google 4.8 Host since we track it anyways
* Graphite Flags (With call options I brought along from watching SaberMod development)
* Many other gcc flags to optimize the build also tucked away in cc-call options to keep clang from touching them and erroring out.

Note: Strict Aliasing is not included but I'll look into adding it in the future.

To use Place flag LIQUIFY=true in BoardConfig.mk of your device tree.

Signed-off-by: Chet Kener <Cl3Kener@gmail.com>
Change-Id: Ia27cc2f5a8be14df3173d4813509baa8d90d7fff
Merge "LIQUIFY OPTIMIZATIONS V1" into lollipop
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

Change-Id: I40f8c8dbd2a8a84a5c1b9f47ee04180a71ef4e07
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
build: Fix PreBuilt Chromium refs

Change-Id: Icc553d5be1e71d8c754bc85b6906252e5690b508
Address armv7-a-neon config issues

1) CM by default removes krait from cortex-a15 but if you look at Google build master branch they leave this note about how it is needed so that hardware divide operation are generated. This should resolve that issue.
2) It turns out that krait/cortex-a15 support LPAE but it is not enabled unless we fake this flag here.  This is also from Google build Master Branch.
3) I noticed that --fix-cortex-a8 is being applied to all cpu varients which makes no sense so I've moved that option under cortex-a8 where it should be (at least in my opinion where it should be)

Signed-off-by: Chet Kener <Cl3Kener@gmail.com>
Change-Id: I3aa5266dab8ab23267623ca936f771edbae2c9a8
build: Parse TARGET_COPY_FILES_OVERRIDES late in the setup

Change-Id: Ie3e4a168ff224e3b65e4627c0757e8813a02167f
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
Merge "Address armv7-a-neon config issues" into lollipop
"LRX22D"
"LRX22E"
DO NOT MERGE.  Bump version to 5.0.2.

Change-Id: Ia6426dd03ac3b51061429b7da36e317bd3503775
"LRX22F"
LRX22G
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