I'm kinda surprised nobody jumped in on this one; either my question is so silly it isn't worth anyone's time, or I'm the only one who wants to add packages to an image after a full build. I know my question has nothing to do with trace-cmd specifically, adding any package after a full build results in the same problem.
It would certainly seem odd that the yocto workflow assumes you always know 100% ahead of time which packages you want in your final image. I know when I was playing around with Hob this wasn't an issue: I would simply add the new packages and Hob would build them and add them to the image. >From what I have seen from skimming the documentation, the documentation talks at length about how to add a new package to the configuration, but it doesn't say what commands to issue after modifying the config files. Obviously running "bitbake <image>" alone doesn't work. On Fri, Nov 23, 2012 at 1:27 PM, Trevor Woerner <twoer...@gmail.com> wrote: > There have been many emails and lots of documentation describing how > to add a package to a build, and that's all great. > > Today I was playing around with an image I had already built and > decided I wanted to add a new package to the mix: trace-cmd. I added " > trace-cmd" (with the required leading space) to IMAGE_INSTALL_append > and re-ran my "bitbake <image>" command. > > It failed: > > Unable to resolve package trace-cmd > > If I perform: > > $ bitbake trace-cmd > > and then > > $ bitbake <image> > > it works fine. What am I missing? > > As it turns out, if I knew before my first build that I wanted > trace-cmd, I could have just added it as described above and > everything would have worked as well. > > Best regards, > Trevor _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
