[OE-core] [poky] Need help to build poky image for beagle board

[Richard Purdie]

On Mon, 2011-03-21 at 12:49 +0100, Koen Kooi wrote:
> Op 21 mrt 2011, om 11:29 heeft Sparsh Wid hope het volgende geschreven: 
> > I'm trying to build poky image for beagle board. 
> 
> I'll address the 'beagleboard' portion of your question below.
> 
> > I got the following error- 
> > FATAL: Error when parsing []: file classes/packaged-staging.bbclass not found in /home/surya/Surya/pro/POKY/meta-texasinstruments:/home/surya/Surya/pro/POKY/meta
> > 
> > I followed the steps below-
> > 
> > 1.Downloaded the source 
> > wget -c http://git.pokylinux.org/cgit/cgit.cgi/poky/snapshot/poky-laverne-4.0.1.tar.bz2
> > 
> > and rename it as POKY.
> > 2. Get TI's overlay
> > git clone git://github.com/mrchapp/meta-texasinstruments.git
> > cd meta-texasinstruments
> > git checkout -b gitomapzoom --track origin/gitomapzoom

As others have said, this is an older metadata layer which was written
by some people at TI for older versions of Poky. Its not really been
updated in a couple of years. If you really want to use that layer, you
need to use it with the version of Poky it was written for. I'm not sure
offhand which that would be but its a very early development of our
layer technology and we're getting better at handling documenting the
depedencies and working on a more automated way to handle this.

> That's not a TI overlay, it's an overlay done by someone to add the
> dspbridge stuff to OE. If you want better beagleboard support, use the
> following layer:
> 
> http://gitorious.org/angstrom/angstrom-layers/
> 
> If you don't want to manually resolve all the layer dependencies have
> a look at the scripts mentioned in the readme:
> 
> http://gitorious.org/angstrom/angstrom-layers/blobs/master/README
> 
> The 'better' in the above is aimed at hw support like cpufreq, DSP,
> 1GHz/720MHz, etc. The standard yocto kernel lacks all that because
> it's focussed at different things like 100% POSIX compliance.

Right, Yocto decided to use the beagleboard hardware as a hardware
target to demonstrate that its core arm support was good.

We've therefore been looking at things like POSIX tests, LSB compliance
and also some of the tooling benefits from the Yocto kernel such as its
defconfig management, integrated lttng support and other features. In
the meantime, the hardware component support in other layers has vastly
improved which is great.

I'm hoping we'll find ways to get the best of both worlds in future and
we're looking at ways of making that happen.

Cheers,

Richard