ah we do the combining of the two images in a postprocess step after the 2nd image...
but I wonder if we are to make a dummy preprocess step that will make a difference... not sure why that would work. we'll give it a try.. which version of bitbake are you using? On Tue, Feb 9, 2010 at 10:36 AM, Cedric GESTES <[email protected]> wrote: > Yes we succeeded but this is far from being optimal in our case. > > We have two recipes: opennao-image and nao-initramfs-image. > > In opennao-image.bb: > > DEPENDS = "nao-initramfs-image" > IMAGE_PREPROCESS_COMMAND += "do_copy_initrd" > > do_copy_initrd() { > install -d ${IMAGE_ROOTFS}/boot > install -m 0644 ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME_RD} > ${IMAGE_ROOTFS}/boot/initrd > } > > > This will do ther trick. > > On Tue, Feb 9, 2010 at 7:06 PM, C Michael Sundius <[email protected]> > wrote: > > In otherwords has anyone had any success with making one image depend > upon a > > 2nd image? > > > > if you what did you do to make that work. > > mike > > > > > > On Mon, Feb 8, 2010 at 4:37 PM, John Van Horne (vanhorj) > > <[email protected]>wrote: > > > >> The system I'm working on boots up with an initramfs image which > >> contains a very minimal file system. During the boot process, a second > >> file system image, in cramfs format, is mounted and used as the root > >> file system. Does anyone have any experience using OE to build such an > >> image? My approach to this was to have a recipe for the cramfs image and > >> a recipe for the initramfs image, and to list the cramfs image as a > >> dependency of the initramfs recipe. Both of these recipes inherit the > >> image class. However, running bitbake on the initramfs recipe fails > >> because the cramfs do_rootfs and do_deploy_to tasks have not run. After > >> running bitbake with debug info turned on, it seems that the initramfs > >> recipe depends upon the do_populate_stage task of cramfs, but not > >> do_rootfs and do_deploy_to. Could anyone offer any insight into why this > >> is? > >> > >> > >> > >> Thanks > >> > >> -John > >> > >> _______________________________________________ > >> Openembedded-devel mailing list > >> [email protected] > >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > >> > > _______________________________________________ > > Openembedded-devel mailing list > > [email protected] > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > > > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
