Re: Building a core-image-base

[Tomas Frydrych <tf+lists.yocto@r-finger.com>]

Hi,

On 30/08/12 18:48, Denys Dmytriyenko wrote:
> On Tue, Aug 28, 2012 at 06:22:08PM -0400, Sebasti?n Bas Kana wrote:
>> I'm using Yocto/Poky and I'm trying to build an image for my Gumstix Overo.

Worth noting that meta-ti is not compatible with Yocto in numerous
subtle ways that you will have to work around; for example, in addition
to the things you noted, you might, want to add
'TOOLCHAIN_PATH="${STAGING_BINDIR_TOOLCHAIN}"' to your local.conf, or
some other suitable config location, as various meta-ti packages will
fail to compile without it.


> Not sure what was the problem with netbase, as it's quite self contained. Are 
> you sure you are using matching branches?

The problem is that meta-ti seems to be an endlessly moving target
tracking the master of oe core, while people using Yocto tend to use its
stable releases. meta-ti would really benefit from some formal release
process/schedule, but I guess as long as TI considers it to be a
community project only, this is unlikely to happen.


> Either way, you may be better off composing your own image recipe, if you 
> don't want to enable additional layers.

You don't have much of a choice here; you will need to pick some of
these packages from meta-openembedded into a layer of your own as for
now combining meta-openembedded with Yocto does not work; hopefully this
will be resolved at some point.

Tomas