Menu
Until now, I am still really confused between the recipes in Openembedded-core vs the one in meta-openembedded. And many time, have trouble to put the recipes in the right directory. They are really similar yet seem to be so different in the content of recipes.
OpenEmbedded Core contains base layer of recipes, classes and associated files that is meant to be common among many different OpenEmbedded-derived systems, including the Yocto Project.
meta-openembedded is a collection of layers for the OE-core universe
What are the differences of content of these two metadata? And why do they have to separate into two metadata?
533
OpenEmbedded is the recommended build system of the Yocto Project, which is a Linux Foundation workgroup that assists commercial companies in the development of Linux-based systems for embedded products.
Difference Between Yocto Project Poky and OpenEmbeddedPoky is the reference operating system distribution built with Yocto Project tools, and OpenEmbedded is a build framework of recipes and packages. OpenEmbedded supports many hardware architectures with cross-compilation infrastructure.
meta-data means conf, classes, and recipes. e.g: meta-fsl-arm is a meta-layer which contains the meta data(configuration and mechines classes and all recipes ) meta-phytec is a layer which contains the meta-data(like conf files, classes, and all recipes)
Poky is a reference distribution of the Yocto Project®. It contains the OpenEmbedded Build System (BitBake and OpenEmbedded Core) as well as a set of metadata to get you started building your own distro. To use the Yocto Project tools, you can download Poky and use it to bootstrap your own distribution.
At the start of the OpenEmbedded Project, there was only one set of recipes. By 2010, the sheer size of the meta-data was a problem. (You can see the old repository here: https://github.com/openembedded/openembedded)
The start of the Yocto Project provided manpower to do something OpenEmbedded had talked about for years, start splitting the recipes into useful and easier to maintain subsets. Openembedded-core are the set of recipes that most people need to use to build a small, useful embedded device. Meta-openembedded was everything else. The meta-openembedded layers are used to extend the capability of openembedded-core by increasing the number of recipes to build more software for your project.
Since then, we have been working on meta-openembedded to divide it into smaller groups of recipes grouped by technology, which is why meta-openembedded contains several layers now.
125
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
