From: <ad...@st...> - 2013-01-15 16:29:17
|
Hello I have a question about available Gumstix build systems. On the Gumstix main page there is an article about Open Embedded, I used it once and as I understand it, this is complete build system with bitbake recipes for many kernels and some libraries and software. But on this mailing list people are mentioning Yocto. Could someone explain to me, what is the difference between Open Embedded and Yocto? If both Yocto and Open Embedded are build systems, which of those have the newest recipes for Gumstix and which one is preferred? Also, what are those layers that people are mentioning in connection with Yocto? If those questions are very basic and trivial - I am sorry, but I wanted to do some development on Gumstix board and I am somewhat confused where should I start now if I wanted to cross-compile kernel and/or create some new rootfs and benefit from ongoing evolution of Gumstix "ecosystem" so to speak. Best Regards Andrzej |
From: Steffen H. <s_...@cs...> - 2013-01-16 14:17:52
|
Hello Andrzej, maybe the following sources help you understanding the differences as they help me with nearly the same problem: http://www.aosabook.org/en/yocto.html http://blogs.mentor.com/chrishallinan/blog/2012/04/13/yocto-versus-poky-versus-angstrom-etc/ http://blogs.mentor.com/chrishallinan/blog/2012/04/27/more-on-yocto-terminology-recipes-and-packages/ And of course the official Yocto documentation ;-) Regards Steffen Am 15.01.2013 17:10, schrieb ad...@st...: > Hello > > I have a question about available Gumstix build systems. > > On the Gumstix main page there is an article about Open Embedded, I > used it once and as I understand it, this is complete build system with > bitbake recipes for many kernels and some libraries and software. > > But on this mailing list people are mentioning Yocto. > > Could someone explain to me, what is the difference between Open > Embedded and Yocto? > > If both Yocto and Open Embedded are build systems, which of those have > the newest recipes for Gumstix and which one is preferred? > > Also, what are those layers that people are mentioning in connection > with Yocto? > > If those questions are very basic and trivial - I am sorry, but I > wanted to do some development on Gumstix board and I am somewhat > confused where should I start now if I wanted to cross-compile kernel > and/or create some new rootfs and benefit from ongoing evolution of > Gumstix "ecosystem" so to speak. > > > Best Regards > Andrzej > > ------------------------------------------------------------------------------ > Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS > and more. Get SQL Server skills now (including 2012) with LearnDevNow - > 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > SALE $99.99 this month only - learn more at: > http://p.sf.net/sfu/learnmore_122512 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Trevor W. <two...@gm...> - 2013-01-16 14:58:15
|
Steffen provided excellent links to help get you going. But if I could add my $0.02... A long time ago the gumstix community used buildroot to build its images. Then they switched to OpenEmbedded (OE). Originally OE was designed to create a root filesystem for one specific (non-gumstix) device. As others started using it to try to create filesystems for their devices OE quickly showed design issues making these sorts of changes hard. So a new redesign of OE appeared, and the original OE is now called "OE Classic", but at the same time others were creating their own versions of OE. At around the time the new OE appeared the Yocto Project started (YP). The YP exists under the Linux Foundation and is an attempt to bring everyone back into one fold and make it easier for everyone to create images for their own devices. As part of making it easy for everyone to use, instead of having one massive repository that includes recipes for every manufacturer, CPU, eval board, library, tools, etc combination in the world, YP has this concept of "layers". Yocto provides a base toolset, kernel, and software to get you started, but is designed such that others can add "layers" on top of the base. Sometimes theses layers add new things; other times these layers override things in the base Yocto. In any case, the purpose of a layer is to do all the specific things necessary to create an image for a specific device. However, in much the same way a layer can be used to target a specific device, sometimes a layer can be used to add a specific feature (such as systemd). On Tue, Jan 15, 2013 at 11:10 AM, <ad...@st...> wrote: > On the Gumstix main page there is an article about Open Embedded > If both Yocto and Open Embedded are build systems, which of those have > the newest recipes for Gumstix and which one is preferred? If the Gumstix website still mentions OE that would be a mistake, wouldn't it? I believe Yocto is the "official" build system endorsed by Gumstix and the gumstix community. References to OE on the Gumstix website should only be there for historic purposes. Gumstix development stuck with OE-Classic long after others had moved away to new OE or other build systems. Now that Yocto is gaining popularity and traction in the embedded community, Gumstix has moved away from OE-Classic and is using Yocto with its own official layer so it can be used to build images for Gumstix devices. ...at least that's how I remember it and in theory this is how it should all work ;-) |