On 2015-03-27 18:10, Matt Schuckmann wrote:
I’ve run into this a couple times now and I still don’t get it so please help me understand. I’m trying to understand how to include just the ir-keytable package of the v4l-utils_1.6.2.bb recipe. At first I was getting a lot of “Nothing PROVIDES” or “Nothing RPROVIDES” error messages when I tried to add it to a package group or as a dependency of another recipe. However, after I added it directly to IMAGE_INSTALL in my image recipe it mostly seems to be working, no matter where I put it, even after I’ve removed it from IMAGE_INSTALL in my image recipe. This leads me to believe that maybe I had some sort of database caching problem going on, since I had just back ported the recipe into my branch. Where it still fails is from the command line: “bitbake ir-keytable” I don’t understand why this fails?
The reason is that you bitbake <recipe>, not the package name. The v4l-utils recipe creates, among other packages, the ir-keytable package. It works when you add it to IMAGE_INSTALL because that contains a list of packages, not recipes.
I’ve had similar problems with the sub-packages of the boost recipe, I can add it boost-program-options to a packagegroup or as a RDEPENDENCY but I can’t build it from the command-line. On the other hand I can build net-snmp-server from the command line, which is a sub-package of net-snmp recipe (interestingly there is no net-snmp package) I looked at the recipes and they don’t seem all that different as far as how the packages are declared. I’m really confused here can anyone enlighten me.
-- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
