[oe] getting started - docbook

Cliff Brake cliff.brake at gmail.com
Thu Oct 25 17:34:51 UTC 2007


On 10/25/07, David Farning <dfarning at gmail.com> wrote:
> On Thu, Oct 25, 2007 at 09:37:39AM +0200, Koen Kooi wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > David Farning schreef:
> > Actually they aren't the same :)
> >
> > A bitbake file and a recipe are the same thing, but they produces a
> > package (.ipk, .deb, etc). That's why we have DEPENDS (for the recipe)
> > and RDEPENDS (for the package).
>
> At least on place in either the bitbake or oe manual, the stuff under
> the dev/packages/ is referred to as packages.
>
> In the bitbake help, the usage is show as $bitbake [option] [package].
> How can base-task of gpe-image be a package.
>
> I know this this sounds really picky;)

No, we need to be consistent -- this is a good exercise.  Perhaps
<oe>/packages should really be <oe>/recipes.

> But I am struggling over what to call the object of a bitebake.  (In
> make they are call targets .ie make all, but in the embedded world
> target is used to refer to the device for which you are building.)
>
> $bitbake vim
> $bitbake task-base
> $bitbake gpe-image
> $bitbake world
> A package, a task, an image, and world?

I suppose it depends -- saying that I'm "building a packages" is
technically correct as the ipk/deb is the output.  But, "bitbaking a
recipe" is probably more correct.

perhaps recipe -- that way it is very obvious what we are talking about.

Cliff

-- 
=======================
Cliff Brake
http://bec-systems.com




More information about the Openembedded-devel mailing list