> From: Anders Darander > > > So is there a general way to peruse the collection of > recipes? Does one have > > to do "ls -R *.bb" to get the list of recipes, then read > the comments inside > > the files to see how to use them? > > No, the recipes themselves do not enforce their own > inclusions into your > image. (That wouldn't really make sense, especially not when including > such a large layer as meta-oe). > > > And how does one know in advance which ones get included by > default? Is > > there some construct one looks for in the .bb file that > indicates it gets > > included? Or is there some master recipe that says "this > depends upon this > > big long list of standard recipes"? > > Which image are you building? > > Say that you're building core-image-sato, then you'll have to look at > that recipe meta/recipes-sato/images/core-image-sato.bb. > > There you might find IMAGE_INSTALL, which defines what packages (and > package groupds) this recipe wants to install. > > The recipes can also define IMAGE_FEATURES, which are used by the > core-image.bbclass (which is inherited in the .bb-file), to > add a number > of packages. > > > And are any of the recipes that are included by default not actually > > required, and if so, how do you un-include them if you want > to pare down the > > system to a bare minimum? > > Sure, there's likely some stuff in most images that you're not > interested in. All the supplied images are there for some use-case, be > it demoing stuff, test, etc. > > If you want to customize an image more, I'd recommend you to > create your > own image. A first step might be to just copy one of the image recipes > to a layer of your own, and then modify it according to your taste.
Thanks. With everyone's help, the fog is gradually lifting. -- Ciao, Paul D. DeRocco Paul mailto:pdero...@ix.netcom.com _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
