image.bbclass: IMAGE_VARS->IMAGE_BOOT, make overridable
authorRoman I Khimov <khimov@altell.ru>
Thu, 16 Apr 2009 01:47:01 +0000 (01:47 +0000)
committerKoen Kooi <koen@openembedded.org>
Tue, 21 Apr 2009 20:45:36 +0000 (22:45 +0200)
IMAGE_VARS usage forces images to have init, dev management, login
management and other stuff. In cases where you don't need any of those
(like initramfs images or other special-purpose images) you need to
override 4 variables in order to get clean image that only installs
things from IMAGE_INSTALL.

So, this changes IMAGE_VARS to more meaningful IMAGE_BOOT and makes it
possible to build images without boot components with single
IMAGE_BOOT="".
Acked-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Koen Kooi <koen@openembedded.org>
classes/image.bbclass

index 3a0bc32..cbbbbd1 100644 (file)
@@ -17,16 +17,16 @@ IMAGE_INITSCRIPTS ?= "initscripts"
 #
 IMAGE_LOGIN_MANAGER ?= "tinylogin"
 
-IMAGE_VARS = "${IMAGE_INITSCRIPTS} \
+IMAGE_BOOT ?= "${IMAGE_INITSCRIPTS} \
 ${IMAGE_DEV_MANAGER} \
 ${IMAGE_INIT_MANAGER} \
 ${IMAGE_LOGIN_MANAGER} "
 
-RDEPENDS += "${IMAGE_INSTALL} ${IMAGE_VARS}"
+RDEPENDS += "${IMAGE_INSTALL} ${IMAGE_BOOT}"
 
 # "export IMAGE_BASENAME" not supported at this time
 IMAGE_BASENAME[export] = "1"
-export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${IMAGE_VARS}"
+export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${IMAGE_BOOT}"
 
 # We need to recursively follow RDEPENDS and RRECOMMENDS for images
 do_rootfs[recrdeptask] += "do_deploy do_populate_staging"