releasetools: Add support for BML partition type

Needed for Samsung devices using proprietary FSR drivers.
Backported from gingerbread branch.

Change-Id: I59f9da9c4832f791f2e126257d2ed777d6104ad8
add unpackbootimg to otatools

Change-Id: I4e294c05eacc8bef8273247bcf1bf382291a3d31
This is causing generic_armv5-userdebug builds to fail. Commenting out for now to fix recovery build servers. Will fix properly later.

Change-Id: Ibe1cda8cd2b4c1914dfa3b8a29724c9069e047a6
build: display the full path of the installed libs, to allow copy paste

Change-Id: If897dc1784d7fb6991e0b22f8b25da19445b571c
Does not copy anything

Change-Id: Ic11859144c9ba226312fd70fb5697d43d49c1e7d
Fix up the get-file-size function that was broken due to the prior commit that made it utilize gnu stat (gstat)

Change-Id: I24bba2bfcb509ad1ad76d2260eedd685ba45c393
Use less heap space for dex on 32-bit build hosts

Run dex with -JXmx1024M instead of 2048M if running on a 32-bit host.
Surprisingly this appears to also work for framework and services; if
not, a little fine-tuning will be needed.

This does not change anything for non-32-bit hosts.

Change-Id: I1d87c3e394acc934af6f7770ea54ba265a1df838
Make the recovery ramdisk target depend on $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_FILES) rather than $(INSTALLED_BOOTIMAGE_TARGET). This fixes the circular dependency for when the kernel depends on the recovery ramdisk, which depends on the boot image, which depends on the kernel.

Change-Id: I658bedc329f2ea0170ac0012f80ca7d779b1c242
build: fix target header overlay

LOCAL_C_INCLUDES as defined by the makefile should be put AFTER
the overlay includes so the overlay always takes precedence.

Change-Id: I489b2aab6dbacd9122d834f85e07b63ed1271f07
Fix "build: display the full path of the installed libs, to allow copy paste"

When OUT_DIR is not "out", it'll show the wrong path, as the out dir
won't be under ANDROID_BUILD_TOP

This fixes commit 80970297312c426f326284e81869db8a2cf8a487.

Change-Id: Ie8610ec5e1e4ae570a64fba9168a686bfe929961
unpackbootimg: add a target specifically for unpackbootimg.
for some reason, and I am guessing this is a bug in the Android build, I can no longer run the following:
make -j32 out/host/darwin-x86/bin/unpackbootimg

It works if the build has been built, but not if it is clean. Somewhere within the bowels of AOSP
something broken in 4.1.2.

Change-Id: I4f8c434f3fce9ddaee4f54febba02efac07a31a3
fix sdk target with absolute OUT_DIR

Add / to atree's search path.

since I459a3b13 OUT_DIR is absolute. atree uses these variables and
due to "-I ." tries to resolve these paths as relative paths.

Change-Id: Ic9fbc84acdd9f438dfc813f6496e2c5e0d761976
Fix SmokeTest

Change-Id: Ia53766b62d3777de49eaaac122042b99e6f1a3f7
Add ARMv6J and ARMv6-VFP processor combo option

Cherry-picked from gingerbread branch.
Add recoveryzip target. Import recovery building/porting tools.
create a target for utilities
Fix up the autoinclusion rules for the utilities and recoveryimage target.
ota: Build uboot bootable images when necessary
build: Add support for assembling multi-image uboot files

Change-Id: I7300d36cc4227ada77f1800680869037ef33c5e8
Extract uboot image creation from core/Makefile

http://memegenerator.net/instance/12495768

This change utilizes BOARD_CUSTOM_BOOTIMG_MK to extract out the Uboot boot and
recovery image generation out into it's own file (approx 130 lines).

This should:
    * Clean up the already huge Makefile and the keep ifdeffyness down
    * Make sure Uboot changes don't effect other builds
    * Extract a lot of code that is only for 3 devices

This depreciates BOARD_USES_UBOOT but BOARD_USES_UBOOT_MULTIIMAGE is still valid.

Boards who use uboot boot images should remove BOARD_USES_UBOOT and add
  BOARD_CUSTOM_BOOTIMG_MK := device/common/uboot-bootimg.mk
to their BoardConfig.mk
(location of the makefile is not finalized)

Change-Id: I90505a99cbcda11731ac3318cfe7f76b4bf6e1c7