openembedded

I'm trying out yocto (2.0, jethro) and I want to build an image starting from core-image-minimal . This works fine. Every website out there mention modifying the file build/config/local.conf with (some of) my customization. For example, the target machine (through MACHINE ) or some global settings (through EXTRA_IMAGE_FEATURES ). I also need to modify some specific packages and the way to do it is to create a custom layer. So far so good. What I don't understand is how to "save" all my configuration to version control. I want everything I change to be locate in files that I can commit so that

I wish to add more python modules to my yocto/openembedded project but I am unsure how to? I wish to add flask and its dependencies. some python packages having corresponding recipes in the meta folders, like Enum class for example: meta-openembedded/meta-python/recipes-devtools/python/python-enum34_1.1.6.bb unfortunately lot's of useful classes aren't available, but some might be needed for the python application. get used of installing missing packages using pip already on booted platform? but what if the target product is not IP network connected? the solution is to implement a new recipe

I've been trying to build and boot OpenEmbedded-Core on the evaluation kit for Freescale's ARM i.MX28 , using the Freescale ARM layer for OpenEmbedded-Core . Unfortunately, I can't find a basic "Getting Started" guide (though there is a Yocto getting-started guide ). Unfortunately, I haven't been able to "get started", to the point of successfully booting to a basic command prompt on the board's debug serial port. Here is what I've been able to piece together, and as far as I've managed to get so far. Fetch sources mkdir -p oe-core/freescale-arm cd oe-core/freescale-arm git clone git://git

I would like to build a Docker image without docker iself. I have looked at Packer , but it requiers to have Docker installed on the builder host. I have looked at the Docker Registry API documentation but this information doesn't appear to be there. I guess that the image is simply a tarball, but I would like to see a complete specification of the format, i.e. what exect format is required and whethere there are any metadata files required. I could attempt downloading an image from the registry and look what's inside, but there is no information on how to fetch the image itself. The idea of

I am trying to build an yocto image with my own package. I have OpenCV code on github which uses cmake. I trying to write a recipe for it and facing lot of errors. Can any one give some hints on what functions or parameters to include in my recipe. My recipe looks as following DESCRIPTION = "cameracapture application" SECTION = "examples" LICENSE = "CLOSED" PR = "r0" DEPENDS += "opencv" SRC_URI = "git://https://github.com/zafrullahsyed/cameracapture.git;protocol=https;tag=v0.1" EXTRA_OECMAKE="" do_configure() { cmake ../ } inherit pkgconfig cmake I followed these tutorials to write my recipe

I work with the Yocto Project quite a bit and a common challenge is determining why (or from what recipe) a file has been included on the rootfs. This is something that can hopefully be derived from the build system's environment, log & meta data. Ideally, a set of commands would allow linking a file back to a source (ie. recipe). My usual strategy is to perform searches on the meta data (e.g. grep -R filename ../layers/* ) and searches on the internet of said filenames to find clues of possible responsible recipes. However, this is not always very effective. In many cases, filenames are not