Mark Hatle said: > Yocto is a cross-compiled build environment. This is a departure to a lot > of the Moblin/MeeGo work that has occurred in the past. The advantages are > you can use any commodity PC to target any (supported) architecture. > Disadvantages are that when you introduce new code, you need to ensure > that it has a recipe (build instructions for bitbake) and can cross > compile. If everyone has to do the same work over and over, this can be > time consuming and counter productive. If people work together, the time > and support burden are dramatically reduced. This can help negate issues > people have had in the past with cross compiling. Note: Yocto -does- have a > self hosted compile environment if it is needed, this is usually when cross > compiling isn't easy to do for some reason. >
Mark & everyone else listening: Would you say that (1) the need for a recipe and (2) the requirement to cross-compile are two of the most major usability or learning-curve disadvantages of working with the Yocto Project (and oe-core)? What would be a third disadvantage from a usability standpoint? Another way to put it: if you could change three things about the Yocto Project to make it more approachable for someone who has never used it before, what would they be? -- Jeff Osier-Mixon http://jefro.net/blog Yocto Project Community Manager @Intel http://yoctoproject.org
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
