clockwwork recovery build fixes
fix BOARD_CUSTOM_BOOTIMG_MK
Allow a device to generically define its own headers

We have a few cases of devices including specific versions of projects
just because of modified headers (msm_mdp.h comes to mind), and I just
had enough of ifdeffing header files for specific cases (the P990 needs
a lot of these).
Now... if a target defines a TARGET_SPECIFIC_HEADER_PATH, any headers in
there will take precedence over the standard ones; for example, on the
p990, I have

TARGET_SPECIFIC_HEADER_PATH := device/lge/p990/include

which makes, for example, the
device/lge/p990/include/hardware_legacy/AudioHardwareInterface.h be
used instead of
hardware/libhardware_legacy/include/hardware_legacy/AudioHardwareInterface.h
whenever a source file uses <hardware_legacy/AudioHardwareInterface.h>

Change-Id: I41b62668b60e3f62a6ebd3738d8d2675103a81e6a
ota: Remove cruft we don't care about

Skip the date check (downgrade to your content), and don't include
recovery in otapackages.
ota: Build uboot bootable images when necessary
armv7-a build: allow for board customization of CPU/FPU target

to cover the entire gamut of CPU and FPU compilation types possible
with ARMv7 (uniprocessor vs SMP, no-FPU vs VFPv3 vs Neon, A8 work-
arounds required vs unnecessary), the compilation codepath needs to
be specified by the BoardConfig.mk to ensure that the OS matches the
target hardware.

add TARGET_ARCH_VARIANT_FPU, TARGET_ARCH_VARIANT_CPU and
TARGET_CPU_SMP makefile variables to allow for target-directed
compilation flags.

Change-Id: Ie968b3d9a4dff0020671725da2b5a6b42fec8a28
fix up ota_from_target_files symlink detection.
envsetup: cmremote,cmgerrit,cmrebase,mka,reposync

    Add the cm specific functions (cmremote, cmgerrit, cmrebase,
    mka, reposync) that are present in the gingerbread branch

Change-Id: If28a5a206b8bb9ead5242c60f6c1e6af27141b57
make bacon and custom releasetool (for squished zips)

Change-Id: I4f61b6a6b9b8bab8582fa5423c4134c07af17606
Merge "fix up ota_from_target_files symlink detection." into ics
Merge "make bacon and custom releasetool (for squished zips)" into ics
HOST_linux-x86: Avoid doubly define macro _FORTIFY_SOURCE

While building Android with latest host gcc, it causes the following
build error:

Install: out/host/linux-x86/bin/mkbootimg
host C++: obbtool <= frameworks/base/tools/obbtool/Main.cpp
<command-line>:0:0: error: "_FORTIFY_SOURCE" redefined [-Werror]
<built-in>:0:0: note: this is the location of the previous definition
cc1plus: all warnings being treated as errors

In order to make build system happy, this patch does unset macro
_FORTIFY_SOURCE and then define it in host cflags.

Change-Id: Ic37a90f05081a2c3650b3335bc87e9e895900fb2
Add a hash-bang as the first line of a shell script

Change-Id: I5b663b036ecb25e952ecd2d998971cc326d4ebdf
Place linker arguments after objects for gcc

gcc 4.6.1 does not properly link if libraries are specified before
objects.

Change-Id: Iabe3eac831fe597abe8a93a946ab7a22d584db46
Add ext2, ext3, and vfat to releasetools

Support some non-standard partition that may be found in recovery.fstab

Change-Id: I0026a1d3ae5d432db10150d1a15f7bc8e7a6054b
build: allow use of openjdk and other versions of make

Change-Id: I2e3c7f89ce51888afb9cda30eeaf6d757b057e2e
Add recoveryzip target. Import recovery building/porting tools.
add support for overriding build.prop settings.

Change-Id: Ie4224d608b7bcb0c2087bd77bc954f8f5f9b6495

Conflicts:

	core/Makefile
CWR does not support writing a partition from memory. Use /tmp to store the extracted file, then write it.
Add ARMv6J and ARMv6-VFP processor combo option

Cherry-picked from gingerbread branch.