Created attachment 4337 [details] sample which shows problem Looks like with Sumo I can not install an empty package anymore on the rootfs, which makes it hard to install it on the SDK;) I have a recipe which generates a .a file. Please check testcase and error in attachment: autotooled-lib-a ├── files │ └── libhw-a-1.0.tar.gz ├── libhw-a_1.0.bb └── readme.txt
Now it's getting spooky;) If I do this IMAGE_INSTALL_append = " libhw-a" SDKIMAGE_FEATURES_append = " dev-pkgs dbg-pkgs staticdev-pkgs" I mean I add the line: SDKIMAGE_FEATURES_append = " dev-pkgs dbg-pkgs staticdev-pkgs" I can bake bitbake core-inage-minimal without any problem and even see it installed: bitbake -g core-image-minimal && cat pn-buildlist | grep -v -e '-native' | grep -v digraph | grep -v -e '-image' | awk '{print }' | sort | uniq contains: libhw-a
Hi Robert, Is this because we disabled static libraries in sumo? That would mean they don't get packaged, the package then becomes empty, empty packages don't get generated and hence you can't install it?
See Richard's question
I did a talk at ELCE Yocto Dev day about this and similar issues (around static libs) and would say this is resolved now.
Yes it's about static (autotooled) libs disabled by default.
From comment #4 it seems as if this is actually fixed now, so I'm closing the bug. If this is not the case please re-open the bug and explain clearly what the problem is: installing empty packages does work as that's what packagegroups are.