When trying to make a sdk-image.bb I noticed an oddity that took me a while to figure out. In my sdk-image.bb I had similar to the following: IMAGE_INSTALL += "libsqlite3" IMAGE_FEATURES ++ "dev-pkgs staticdev-pkgs" sqlite3 has these packages defined within it: PACKAGES = "lib${BPN} lib${BPN}-dev lib${BPN}-doc ${PN}-dbg lib${BPN}-staticdev ${PN}" FILES_${PN} = "${bindir}/*" FILES_lib${BPN} = "${libdir}/*.so.*" FILES_lib${BPN}-dev = "${libdir}/*.la ${libdir}/*.so \ ${libdir}/pkgconfig ${includedir}" FILES_lib${BPN}-doc = "${docdir} ${mandir} ${infodir}" FILES_lib${BPN}-staticdev = "${libdir}/lib*.a" AUTO_LIBNAME_PKGS = "${MLPREFIX}lib${BPN}" However, the dev-dbg class did not pick up that the dev package for libsqlite3 was libsqlite3-dev. I can only assume that it looks for ${PN}-dev, which in this case is sqlite3-dev, but I wanted libsqlite3-dev. Therefore, is this a bug?
Hi Jack, Can you please add the following information: -poky version (or branch + commit) -commands used (ex: bitbake -g <target_recipe>) -some relevant output (in the above example it would be pn-buildlist or package-depends.dot, both produced by the -g option) Note: you can also use the "Version" field.
Ok, I tested this again this morning and it seems I was either being daft the first time round or it was fixed in the meantime. Regardless, it's solved.
verified as per above comment.