Ying Wang 89686538d7 Support to build factory ramdisk image. ... Bug: 5769921 With this change, to build factory_ramdisk.img, set PRODUCT_FACTORY_RAMDISK_MODULES in your product config. PRODUCT_FACTORY_RAMDISK_MODULES consists of "<module_name>:<install_path>" pairs. <install_path> is relative to the root of the factory ramdisk output. For example: PRODUCT_FACTORY_RAMDISK_MODULES := \ toolbox:bin/toolbox adbd:sbin/adbd adb:bin/adb On the other hand you can use PRODUCT_COPY_FILES to copy prebuilt files to the factory ramdisk. Or you can define modules that are specific for the factory ramdisk (with LOCAL_MODULE_PATH pointing to TARGET_FACTORY_RAMDISK_OUT) and add the module names to PRODUCT_PACKAGES. Change-Id: I80ff72606415cd74fe6f3bc93020a05d84e45b70		2011-12-16 13:54:10 -08:00
..
apicheck.mk	update to use the new apicheck	2011-04-08 17:32:52 -07:00
cts.mk	Stop Building CTS VM Tests	2011-12-16 13:07:15 -08:00
factory_ramdisk.mk	Support to build factory ramdisk image.	2011-12-16 13:54:10 -08:00
ide.mk	Make make ECLIPSE-lunch build a .classpath for all the java stuff that will be included in the	2010-05-26 17:58:21 -04:00
module_owner_check.mk	Add several module owners to the whitelist	2011-12-15 10:25:17 -08:00
product-graph.mk	Tweak the product graph formatting.	2009-08-08 12:15:10 -07:00
sdk-addon.mk	Google Add-On API Documentation Fixes (5429077)	2011-11-23 18:08:51 -08:00