[meta-ti] building yocto images with meta-ti

Nicolas Dechesne ndec13 at gmail.com
Wed Sep 19 09:04:09 PDT 2012


hi,

thanks for your answers

On Wed, Sep 19, 2012 at 3:57 PM, Denys Dmytriyenko <denys at ti.com> wrote:
> On Wed, Sep 19, 2012 at 08:16:05AM +0200, Nicolas Dechesne wrote:
>> hi there,
>
> Hi Nicolas,
>
>> i was able to build a 'vanilla' yocto image using the yocto git repo.
>> then i wanted to add meta-ti layer. so i have done the following:
>
> First, a little rant... :)
>
> It's unfortunate, but this still causes lots of confusion. Some purists among
> us will say that is not Yocto, but Poky. Case in point - which "yocto" git
> repository you cloned from http://git.yoctoproject.org/ ?

so yes, I meant Poky. It was indeed quite subtle to me, and I didn't
realize there was a difference between yocto and poky ;-)

just to clarify, I had cloned:

git://git.yoctoproject.org/poky.git, commit
913944d904266bf90af0cad94b4f0fb3652bd29d (master)
git://git.yoctoproject.org/meta-ti, commit
9ef35da0c8ff3be8f37214e09d0fc1d4987a11fc (master)

and I had put in my local.conf:

BBMASK = "meta-ti/recipes-misc"

as per the README. I didn't find any other useful information in the
README, though.

is there a good wiki / doc that explains what each of this thing is:
OE vs poky vs yocto vs arago?

is that wrong to expect to be able to build a poky image by combining
meta-ti and poky.git?

>
> Same applies to a 'vanilla' yocto image, which does not exist. It would rather
> be useful to specify which exact image for which MACHINE you are trying to
> build. A little bit more detail is always helpful...
>
>
> And now to the resolution part. I see you already used BBMASK as prescribed in
> the README, since you get past the unset LICENSE error... The below error
> happens when you build for a MACHINE that is overshadowed by another BSP
> layer that does not define MACHINE_KERNEL_PR. This MACHINE_KERNEL_PR variable
> is set in MACHINE definitions of meta-ti BSP layer and then used in other
> recipes within meta-ti and different layers.
>
> In other words, you are trying to build for "beagleboard" machine, which gets
> also defined by meta-yocto-bsp layer, besides meta-ti. The solution is simple -
> you need to move meta-ti above meta-yocto-bsp in your bblayers.conf or just
> remove meta-yocto-bsp from the list, if you are not planning on building any
> of the reference platforms. That way you'll get the machine definition from
> meta-ti layer and not from meta-yocto-bsp.
>
> After that, core-image-minimal and some other images should build fine. Good
> luck!

ok, so based on the feedback, i have moved poky.git to denzil branch,
and meta-ti to denzil branch too. is that expected to be a good
combination?

my build has restarted fine... i will check the build when they complete.

>
> --
> Denys
>
>
>> - clone git://git.yoctoproject.org/meta-ti
>> - modify BBLAYERS in conf/bblayers.conf to add meta-ti
>>
>> i can verify that meta-ti layer is configured properly as
>> bitbake-layers show-layers shows it just fine (with priority 10).
>>
>> However parsing recipes failed with:
>>
>> Loaded 23 entries from dependency cache.
>> ERROR: ExpansionError during parsing
>> /work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager_1.24.02.09.bb:
>> Failure expanding variable FILESPATH, expression was
>> ${@base_set_filespath([
>> "/work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager-1_1_24_02_09-${MACHINE_KERNEL_PR}e",
>> "/work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager-1_24_02_09",
>> "/work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager",
>> "/work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager-1_24_02_09",
>> "/work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager",
>> "/work/yocto/meta-ti/recipes-ti/local-power-manager/files",
>> "/work/yocto/meta-ti/recipes-ti/local-power-manager" ], d)} which
>> triggered exception SyntaxError: EOL while scanning string literal
>> (FILESPATH, line 1)
>> ERROR: Command execution failed: Exited with 1
>>
>> is there a particular commit in yocto that meta-ti requires?
>>
>> how do you guys generate vanilla yocto images with meta-ti?



More information about the meta-ti mailing list