Hi! I'm not quite sure if this is proper forum for my question, but as it somewhat smells a bug, I try first here. I was possibly faced with a bug related to image packing when bitbaking with following configuration: Build Configuration: BB_VERSION = "1.12.0" METADATA_BRANCH = "2011.03-maintenance" METADATA_REVISION = "f9c0bce" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "at91sam9260ek" DISTRO = "angstrom" DISTRO_VERSION = "2011.03" TARGET_FPU = "soft"
One recipe - called recipe-aa_1.0.bb was picked from it's dev packate (recipe-aa-dev_1.0-r0.6_at91sam9260ek.ipk). It was tied in recipe-bb_1.0.bb with RDEPENDS_${PN} =" recipe-aa udev " Then recipe-bb_1.0.bb was included to image in initramfs-image.bbappend with statement: IMAGE_INSTALL_append = " recipe-bb " Anyone followed? Anyhow, everything else goes all right, but recipe-aa is always taken from wrong package (-dev). Could the reason for this be RDEPENDS_${PN} =" recipe-aa udev " statement as there is this 'udev'? Could bitbake use "udev" string to relate recipe-aa with recipe-aa-dev package? Is there any parameter I should use to force using recipe-aa(no -dev) version? Thanks, Matti _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel