Colorize javac errors

 You know those multi-line ones that are frequently
interspersed with other buld output? The ones that don't even have the word
"error" in them to search for?

This makes them red.
Remove extra product property overrides

This appears to clash with vendor/cm/common mk's for overrides; causes
a broken default alarm (and OnTheHunt is so bleh).

Change-Id: I5ec990d3c5ad56b573c45f1a3b20169c989851a0
releasetools: Modify regex for radio files

The filesmap file may contain additional information (such as a
sha1 hash) after the parition name. We should still work in these
cases, but can ignore the additional data.

Change-Id: I0feaa5e94d48fa94b66b6c07e1946674fe703d85
build: Don't build video editor libraries

These are already defined in vendor/cm/config/common_full.mk
We don't want them included in common_mini_* builds
since we don't include video editor there

Change-Id: I7dae9c6736590be8cd080195da4062258ee4a424
releasetools: Add a newline for radio flashing scripts

When multiple radio images exist, make sure we put a newline at
the end of each flash command.

Change-Id: If113c88eb6dc90d2499f06c12e00494d7266a672
build: core: Parameterize recovery with a variant

Include extra vendor config early.  If RECOVERY_VARIANT is set, use it
to look for the recovery in an alternate path.

Change-Id: Iba54f0746d728c0dfeeb67b4d3166d5e25b1b5d7
tools: getb64key - print the base64 version of a PEM public key file

Change-Id: Ia94ff560c88dfe85c3fa55db5c8219aa0d3419ee
Store the base64 release key in the OTA zips

This can be directly grepped in pre-existing package.xml tables
to make sure we're not trying to update to a differently signed
build

Change-Id: I7528a8e7c484ea9209cd665b9263328ae834586a
releasetools: Properly handle boot images that use dt

Instead of using a prebuilt boot/recovery image, bring the dt image
into the target files package and use it during package creation

Change-Id: I70ecf74423aad95a3eb8e085029c37450ae354a2
releasetools: Fix whitespace error for INSTALLED_DTIMAGE_TARGET

Copy/paste produced spaces instead of a tab; fix that

Change-Id: I937e5f6ffd2c947c77dc4baa7427b170c1ea4bcd
Fixes for RECOVERY_VARIANT

call include-path-for, recovery is not working and cwm images and
init.rc are ending up in the image

Change-Id: I48b8118ffe4bb73b601351178b9293327a14740f
Revert "Fixes for RECOVERY_VARIANT"

This reverts commit a63708215a0a1ef4ee7e5294c30fdfc8a1d031ed.
releasetools: bring back boot.img handling

This is required for galaxysmtd and other devices with custom
boot format.

This partially reverts "releasetools: Properly handle boot images that use dt"

Change-Id: Ib35001c2d9b906067e5a3c84712dc3a283a38cbb
build: Add USE_SET_METADATA tag

On some of the older devices the recovery doesn't support
metadata when setting permissions.  This allows to use
set_perm vs set_metadata you will need to set
USE_SET_METADATA := false inside your boardconfig.mk

Thanks to flintman for fix
Merge pull request #4 from WildfireDEV/kitkat1

build: Add USE_SET_METADATA tag
build: use /usr/bin/env to call python

Hardcoding the path to python instead of env is not recommended.  This
can break the build in some Linux environments that link /usr/bin/python
to python3.

Change-Id: I4c62eb391acc6d468ce24ac8640834e965e76e78
Don't warn if using OpenJDK 1.7

OpenJDK is supported if Java version = 1.7
Revert "enable build with linaro 4.7.4 toolchain"

This reverts commit 72fbcfbf65c07126b48db2fe269680cd34a92468.
Merge github.com:ResurrectionRemix/android_build into kitkat1
build: Add new public keys to recovery

Change-Id: I11dea464297813be36e60c23728dde8893535c46