Revert "Add check for local OTA_FROM_TARGET_SCRIPT"

This reverts commit 9dc4e5bdfb1443b4050eb51c00f39dcb2f8a5a03.
Add ext2, ext3, and vfat to releasetools

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

Change-Id: I0026a1d3ae5d432db10150d1a15f7bc8e7a6054b
releasetools: Add support for BML partition type

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

Change-Id: I59f9da9c4832f791f2e126257d2ed777d6104ad8
CWR does not support writing a partition from memory. Use /tmp to store the extracted file, then write it.
Better handling of ramdisk during make

make clobber used to call rm -rf out/
so if out is a soft link to i.e. /tmp/out
the soft link is deleted instead the content
so i changed the makefile to rm -rf out/*

Change-Id: Id1991161617da8ec34307a30412c134e31f589b4
build: Realign product libraries with corresponding applications

VideoEditor requires a build to call the full_base, but the libraries
are called in generic_no_telephony. This patch places the library
packages in the same product specification as the application using
them.
new variable TARGET_RECOVERY_FSTAB

Currently the source file recovery.fstab has to be located
in $(TARGET_DEVICE_DIR)/recovery.fstab).

To allow multiple similar CM products to share one recovery.fstab
file this patch introduces the variable TARGET_RECOVERY_FSTAB.

Change-Id: I51961f5a1665023001c9857e13008a2ca44529ee

Conflicts:
	core/Makefile
releasetools/edify_generator.py Added RunConfig

Added the RunConfig function to the edify_generator for devices
that need the tool.

Credit to CM for the original code.

Change-Id: I191cbdfe890d3e7ed7062498eaceaf7d12bfd7fc
Signed-off-by: Chuck Haines <chaines@codemonkeyjava.com>
add ability to remove device assertions

do this by setting adding "TARGET_OTA_ASSERT_SKIP := true" in BoardConfig.mk

Change-Id: Ia832748ddc00320e0193d93be0883f4cc9208a35

Conflicts:
	core/Makefile
	tools/releasetools/ota_from_target_files
enable TARGET_RELEASETOOL_OTA_FROM_TARGET_SCRIPT for devices with custom releasetools

Conflicts:
	core/Makefile

Change-Id: I96ce64d25b9151b51c858b0b0a22e4a13ae28359
Allow override of device asserts, including multi-device support.

Set in board file with TARGET_OTA_ASSERT_DEVICE.

Conflicts:
	tools/releasetools/ota_from_target_files

Change-Id: I27f89f440bdc4982dcac35631496c865f2657c83
Revert "Load only the current product config makefile."

This reverts commit 54fa8c3ff9b1f0f1b0b9c551be864f1b7378c7fc.

Conflicts:
	core/product_config.mk

Change-Id: Ia942d826eae08429d91bbfbb6c43b1cdd78563f7
Fix build on asserts

Change-Id: Ia28b014ac029a8c8011ab5535aeaea215199c01f
Fix mka for some weird configurations.
Some make versions identify "make -j N" calls as "make N -j <?>" instead
of "make -jN" it was intended to be (a.k.a. the "make 8" error). This
makes sure make -jN is called and also replaces backticks with $() just
for code readability.

Change-Id: I3487a8c92e07cd3a4e07e2642df620ed234516e1
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

Conflicts:
	core/Makefile
Allow Device specific ramdisk address

Change-Id: If0bb3d3a2b51f87a92c0b657fbc6d0277ce53532

Conflicts:
	core/Makefile
Deprecate BOARD_FORCE_RAMDISK_ADDRESS in favor of BOARD_MKBOOTIMG_ARGS.

Change-Id: Ib587f14cb45d752356beec3998a5b956f8b09efa
clockwwork recovery build fixes
fix BOARD_CUSTOM_BOOTIMG_MK
qcom_utils: Only define QCOM_BOARD_PLATFORMS if compiling kernel inline

	* If using prebuilt kernel KERNEL_OBJ/usr will not exist, thus
	  build will complain of dir missing during module compilation

	** Requires TARGET_USE_PREBUILT_KERNEL := true in BoardConfig for now

Signed-off-by: bmc08gt <bmc08gt.teamb00sted@gmail.com>
Change-Id: Iecd8c97e89504c60d2f01926318468ac7eb396f9