[oe] Some help on building a new dist.

Cliff Brake cliff.brake at gmail.com
Mon Jun 18 13:52:46 UTC 2007

On 6/18/07, Pelle Svensson <pelle2004 at hotmail.com> wrote:

> I have playing around with OE and builded some packages ect.
> I have a project that I would like to build with OE.
> Where and how should I start.
> I have a fully working system with rootfs, bootloader, kernel and
> applications
> builded with outside OE with crosstools and some scripts.
> Have I understand OE correctly if it has fully dependency from a the point
> where I issue 'bitbake mysystem'.


> My questions are:
> 1. What 'packages/*/*.bb' file do I need to create.
> Do I need one for putting the rootfs/jffs2 toghether, one for tasks, and one
> for the kernel.
> Where should they be located.

Generally, all you need to do is define:
 - a machine file (conf/machine/<machine.conf>)
 - a local.conf
 - and a kernel

If there are platforms that are close, you may want to start with one of them.

> 2. What is the relation beetween packages files.
> Looking at opie it seems that
> .../images/opie-image.bb <- .../tasks/task-opie.bb <- a huge set of
> 'opie-..' pkg
> I have read this section and the manual for creating new targets
> http://www.openembedded.info/wiki/New_targets#Fileystem_image
> Should I start doing a copy of opie or?
> Have I forgotten anything beside 'local.conf'

local.conf may be enough if you can find a machine that works for you,
or you can put all the machine info in the local.conf file.  I would
not start with opie.  Angstrom is currently maintained and is probably
a better starting point.  I would start with:

bitbake angstrom-console-image

Once you get the console image up and running, then worry about more
complex images, switching to opie, etc.


Cliff Brake

More information about the Openembedded-devel mailing list