Seth – it sounds like you need something different than an overview class. I think you might want to have one of the consultants who are familiar with building projects using the Yocto Project work for you for a couple of days to help you sort these things out, for a fee. I’m sure one of them on this mailing list would be willing to offer their help. (Guys – you know who you are…)
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Seth Bollinger
Sent: Monday, August 20, 2012 7:14 PM
Subject: [yocto] Classes
Will anyone recommend some classes regarding yocto and open embedded? It would be nice to get up to speed quickly and into the nitty gritty instead of an overview.
Something covering the following items would be nice:
1. How should projects be laid out? Distro, image, task, BSP, what things should go where?
2. How should subprojects inherit from superprojects? If you need to create many subplatforms from a base platform, what's the best way to go about this?
3. How should classes such as distutils be created to be inherited by other recipes (ruby modules that require a C extension to be compiled would be one example).
4. How should hardware specific software be handled?
I fear that (as a newb) I will design a layout that will be sub-optimal, but we'll discover that after we have 25 platforms that will need major refactoring. :)