LRX21N
merge in lmp-release history after reset to lmp-dev
"LRX37"
LRX21O
merge in lmp-release history after reset to lmp-dev
LRX21P
"LRX21Q"
Remove nulls from the edify generator.

These would break the scripts. WTF are they doing here?

Change-Id: I0c52335a27f7ae974279fde1c2461b2dba24d263
Add auditd

Change-Id: I54717edbeb9677e53bdd01e6519edd30c387bfe8
build: Automatically set QCOM audio, display, media variants

* Device platform should determing the HAL that ought to be used. This
  commit forces QCOM_HARDWARE to select the -caf HAL variants, which
  are then broken down by platform within the variant path.

Change-Id: I6fc7a3def7b93112f034a3b89552f302727cdbf8
base: build javax.btobex

Change-Id: Ia82f74e7eb0f5758732399064277cf18a1fc15d9
recovery: build uncompressed ramdisk

Change-Id: I6027868864ec2696f20705faf4c68c684e7ef459
Signed-off-by: Chirayu Desai <chirayudesai1@gmail.com>
Remove HomeSample from builds

As good as it looks, we already have a launcher (Launcher3)

Change-Id: I87cac70eec30fd62d6f7ecb7777caa9d240fe0ee
product_config: Set CM_BUILD priority above TARGET_BUILD_APPS

Even if we are doing TARGET_BUILD_APPS, we may want to use a cm
target for building.

Change-Id: Ic8053bc679fa8b726be90e611aeaacdf1850cabc
build: don't clear recovery ramdisk

Clearing recovery ramdisk removes all files place there by the
device tree and all busybox symlinks placed there by recovery

Change-Id: I19e6164856a01a83a6e2c50ef96742edcb9f570f
Merge tag 'android-5.0.0_r5' into HEAD

Android 5.0.0 release 5
build: Enable QCOM_BSP, QC_AV with QCOM_HARDWARE

Change-Id: Ibf9dd35272521109fea52e46bacf6e1e3074ed6a
pathmap: Point QC HAL pathmaps directly to the source

Directly map to the actual HAL directory, including the
board platform. This lets project-path-for point directly
to the respective HALs.

Change-Id: Ic4ed61bbdea9d0b5683502bf84a8410e76858527
Force colorsheme to SVG, since darkblue doesn't exist on X11

Change-Id: I1b9e13dd4ca63ba27a49a55d95130bdceb187669
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.

ps2: fix jar_check failures cause by leaving empty stderr files in intermediates dirs
     this is probably not the best place to store stderr before colorizing it if javac
     exits non-zero, but it seems much lighter than mkdiring a bunch of temp directories
     or using sed to mangle the paths to point to per-intermediates directory unique
     temporary file names

Change-Id: I3b9b7d8a0c76958588ac1603b6742987d6dde54c
Signed-off-by: nuclearmistake <nuclearmistake@gmail.com>