diff options
| author | Ying Wang <wangying@google.com> | 2011-12-16 11:27:52 -0800 |
|---|---|---|
| committer | Ying Wang <wangying@google.com> | 2011-12-16 13:54:10 -0800 |
| commit | 89686538d77c47ed7816594c7597f5d1e456d656 (patch) | |
| tree | 7f2f103ed221046d4c4417a6d490e3ce46a7fe4b /core/envsetup.mk | |
| parent | 1eed1cd4291e9bb2416df2b1e3e29a7493bcec0a (diff) | |
| download | build-89686538d77c47ed7816594c7597f5d1e456d656.zip build-89686538d77c47ed7816594c7597f5d1e456d656.tar.gz build-89686538d77c47ed7816594c7597f5d1e456d656.tar.bz2 | |
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
Diffstat (limited to 'core/envsetup.mk')
| -rw-r--r-- | core/envsetup.mk | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/core/envsetup.mk b/core/envsetup.mk index 3509a8c..74e9100 100644 --- a/core/envsetup.mk +++ b/core/envsetup.mk @@ -253,6 +253,8 @@ TARGET_INSTALLER_DATA_OUT := $(TARGET_INSTALLER_OUT)/data TARGET_INSTALLER_ROOT_OUT := $(TARGET_INSTALLER_OUT)/root TARGET_INSTALLER_SYSTEM_OUT := $(TARGET_INSTALLER_OUT)/root/system +TARGET_FACTORY_RAMDISK_OUT := $(PRODUCT_OUT)/factory_ramdisk + COMMON_MODULE_CLASSES := TARGET-NOTICE_FILES HOST-NOTICE_FILES HOST-JAVA_LIBRARIES ifeq (,$(strip $(DIST_DIR))) |