> > > On Fri, Sep 25, 2015 at 10:15 AM, Allen Curtis > <allen.cur...@curtisembedded.com> wrote: >> I am working with a BSP that has multiple image recipes. >> >> foo-hwbringup-image.bb >> foo-qt5demo-image.bb >> >> foo-qt5demo-image.bb contains "require foo-hwbringup-image.bb" >> >> However if I create foo-hwbringup-image.bbappend, it gets ignored. >> >> What are the rules with appending included recipes? >> >> bbappends do not append arbitrary files, only recipes (and in this case, the >> inclusion treats them as an arbitrary file). They do not apply to anything >> included or required, only the recipe itself. So you'll need to bbappend >> every recipe that includes foo-hwbringup-image.bb in this case. > > This is unfortunate since foo-hwbringup-image.bb is also a valid recipe. It > just doesn't contain the graphics support. > > Is there a better way to add your custom components to "core-image" I guess….. > > You could always define custom features for use in IMAGE_FEATURES and add > them to your images via EXTRA_IMAGE_FEATURES in local.conf, or bbappend one > of the core images.
How is bbappend a core image different from bbappend foo-hwbringup-image? If you follow the original post one more generation, foo-hwbringup-image.bb "inherit core-image"
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
