Re: [yocto] [Draft] From Bitbake Hello World To an Image
Thank you, I enjoyed reading your document. I especially liked the top part which talked about creating your own tasks (which 'turned the light on' for how OE/Yocto use bitbake). I also wasn't aware of the vim helpers which come as part of bitbake. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Draft] From Bitbake Hello World To an Image
I'm not sure if there's something about my system that is different than what you expect, but I had to delete my 'tmp' folder before invoking './bin/bitbake firstrecipe -vDD' after inheriting the autotool versions in order to get the new, overridden tasks to run (since there's no 'clean' tasks). ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Draft] From Bitbake Hello World To an Image
On Thu, Dec 13, 2012 at 05:26:29PM -0500, Trevor Woerner wrote: I'm not sure if there's something about my system that is different than what you expect, but I had to delete my 'tmp' folder before invoking './bin/bitbake firstrecipe -vDD' after inheriting the autotool versions in order to get the new, overridden tasks to run (since there's no 'clean' tasks). Thank you for your feedback. I am glad you like it. You are right that 'tmp' directory needs to be removed after changing the recipe (adding inherit, or removing it). I guess we are hitting bitbake cache. Since clean tasks don't exist, 'tmp' needs to be removed to make changes take effect. I must have removed 'tmp' and missed adding it while writing. I will add the explanation. Regards, Eren -- . 73! DE TA1AET http://linkedin.com/in/erenturkay pgpNVpzkw4DD2.pgp Description: PGP signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Draft] From Bitbake Hello World To an Image
Hello, I have completed a document that tries to explain how image is created using openembedded starting from bitbake fundementals. The document reflects my own understanding and includes the information that I wished to have when I first involved in understanding openembedded. This is aimed for people who want get the big picture with some details under the hood (What's the sequence of creating an image, how is source fetched, patched, configured, and installed? How is ipk, rpm, and deb created? How is image produced?) People who know bitbake can skip to Understanding OpenEmbedded part. However, I suggest them to play with plain bitbake and read the first chapter as bitbake is the hearth of OpenEmbedded. There are additional information required which are marked with FIXME keywords. Suggestions and contributions are welcomed. I don't know how it can be integrated to current documentation but I would like to help if that's the case. The licence of the work is CC BY-SA. Use it, change it, adapt it, distribute it, as long as you attribute the original work and the author :) Document: http://hambedded.org/blog/2012/11/24/from-bitbake-hello-world-to-an-image/ Markdown source: https://github.com/hambedded-linux/hambedded-linux.github.com/tree/source/source/_posts Regards, Eren -- . 73! DE TA1AET http://erenturkay.com/ pgplZR4ZjrBmn.pgp Description: PGP signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
