As part of working on meta-tiny, I've come across a need (want?) to present users with the ability to select some set of features in a local configuration file that will impact the build of the image and a set of recipes.
It is currently possible to affect which packages are installed in an image with variables like POKY_EXTRA_INSTALL. What I'm not finding a way to do is specify some set of features that will impact how a recipe is built. For example, a user may or may not want networking support or virtual terminal support in their image. This impacts both the kernel and busybox (at least). The linux-yocto infrastructure provides us with config fragment functionality, something similar will need to be added to busybox. Access to that is still bound to the machine config by means of the SRC_URI machine override mechanism, but it would be useful to be able to influence it from the image config or the user's local config. For example, when building a tiny image I may decide I do not want VT nor INET support. I might wish to specify this like this (by removing them from the default features): local.conf: #CORE_IMAGE_TINY_FEATURES = "VT INET MDEV" CORE_IMAGE_TINY_FEATURES = "MDEV" I would want this to affect linux-yocto-tiny by dropping the vt.cfg and inet.cfg fragments from the SRC_URI (or from the .scc descriptor files assembled by the linux-yocto meta indrastructure). Busybox would need a similar configuration mechanism, and would also need to add a "no-vt-support.patch" patch to the SRC_URI to avoid a bug/oversight in the busybox init routine. I'd appreciate some help determining the proper bitbake way of doing this. I want to avoid having to create a new machine.conf and/or recipes for every possible combination of features that a user may want to turn on or off. Thanks, -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
