building yocto images with meta-ti

building yocto images with meta-ti

[Nicolas Dechesne]

hi there,

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:

- 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?

thx

Re: building yocto images with meta-ti

[Koen Kooi]

Op 19 sep. 2012, om 08:16 heeft Nicolas Dechesne <ndec13@gmail.com> het volgende geschreven:

> hi there,
> 
> i was able to build a 'vanilla' yocto image using the yocto git repo.

You mean poky, right?

> then i wanted to add meta-ti layer. so i have done the following:
> 
> - 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?

You mean poky, right? Have a look at the README.

Re: building yocto images with meta-ti

[Andrea Galbusera]

Hi Nicolas,

On Wed, Sep 19, 2012 at 8:16 AM, Nicolas Dechesne <ndec13@gmail.com> wrote:
> hi there,
>
> 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:
>
> - 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?

What version of yocto are you using? If denzil is your target, meta-ti
repo has a corresponding denzil branch which should work fine. Having
a look at meta-ti's README is also a good starting point since you
might need to mask some recipes which could not be parsed without, I
think, the meta-oe layer.

I'm personally building core-image-minimal with the following commits:

OE Build Configuration:
BB_VERSION        = "1.15.2"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "wally"
DISTRO            = "poky"
DISTRO_VERSION    = "1.2.1"
TUNE_FEATURES     = "armv5 dsp thumb arm926ejs"
TARGET_FPU        = "soft"
meta
meta-yocto        = "denzil:65ffa7395055f7e012cb973f63f92380828eed0d"
meta-ti           = "denzil:9c103ce85a6ecb836bcdc46137207e466846ee2e"

Regards

Re: building yocto images with meta-ti

[Denys Dmytriyenko]

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/ ?

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!

-- 
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?

Re: building yocto images with meta-ti

[Nicolas Dechesne]

hi,

thanks for your answers

On Wed, Sep 19, 2012 at 3:57 PM, Denys Dmytriyenko <denys@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?

Re: building yocto images with meta-ti

[Trevor Woerner]

On Wed, Sep 19, 2012 at 12:04 PM, Nicolas Dechesne <ndec13@gmail.com> wrote:
> is there a good wiki / doc that explains what each of this thing is:
> OE vs poky vs yocto vs arago?

Chris Hallinan has a blog post that might be helpful:
http://blogs.mentor.com/chrishallinan/blog/2012/04/13/yocto-versus-poky-versus-angstrom-etc/

Re: building yocto images with meta-ti

[Denys Dmytriyenko]

On Wed, Sep 19, 2012 at 06:04:09PM +0200, Nicolas Dechesne wrote:
> hi,
> 
> thanks for your answers
> 
> On Wed, Sep 19, 2012 at 3:57 PM, Denys Dmytriyenko <denys@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 ;-)

It is somewhat convoluted, but in general, Poky is a reference distribution 
and released product built on top of OpenEmbedded-Core. The Yocto Project is 
an umbrella entity for different projects and initiatives based on the common 
infrastructure, such as OpenEmbedded-Core, BitBake etc. There are other 
distributions and projects building on top of OE-Core, such as Angstrom, Arago 
etc., that are supposed to be part of the Yocto Project as well. See Yocto 
Project branding compliance program for official guidelines, that were 
standardized recently... But the Yocto Project Universe is much larger than 
Poky - there are at least 50 different layers that you can mix and match, 
ranging from different BSPs to different Software stacks...


> 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?

Some of that is explained above. I can go into more details offline, if you 
wish.


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

Absolutely not! And I've been building that combination among other things - 
either core-image-minimal or core-image-sato.


> > 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?

Depends on which direction you go. Denzil branch is usually considered more 
stable than master, although master is now feature-frozen for stabilization 
before the next release. Unless you start mixing meta-oe and step on to 
systemd issues, as systemd in denzil is not that clean. Anyway, for a simple 
poky+meta-ti combination and images from meta/ directory it should be fine. 


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

Let us know. Like I said, I've been building both core-image-minimal and 
core-image-sato w/o problems before.

-- 
Denys

Re: building yocto images with meta-ti

[Denys Dmytriyenko]

On Wed, Sep 19, 2012 at 12:26:02PM -0400, Trevor Woerner wrote:
> On Wed, Sep 19, 2012 at 12:04 PM, Nicolas Dechesne <ndec13@gmail.com> wrote:
> > is there a good wiki / doc that explains what each of this thing is:
> > OE vs poky vs yocto vs arago?
> 
> Chris Hallinan has a blog post that might be helpful:
> http://blogs.mentor.com/chrishallinan/blog/2012/04/13/yocto-versus-poky-versus-angstrom-etc/

Heh, it's quite close, but not entirely correct all the time. And not 
complete.

I would agree with and highlight the Poky is a "build system" confusion, 
though!

-- 
Denys

Re: building yocto images with meta-ti

[Nicolas Dechesne]

On Wed, Sep 19, 2012 at 6:26 PM, Denys Dmytriyenko <denys@ti.com> wrote:
> On Wed, Sep 19, 2012 at 06:04:09PM +0200, Nicolas Dechesne wrote:
>> hi,
>>
>> thanks for your answers
>>
>> On Wed, Sep 19, 2012 at 3:57 PM, Denys Dmytriyenko <denys@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 ;-)
>
> It is somewhat convoluted, but in general, Poky is a reference distribution
> and released product built on top of OpenEmbedded-Core. The Yocto Project is
> an umbrella entity for different projects and initiatives based on the common
> infrastructure, such as OpenEmbedded-Core, BitBake etc. There are other
> distributions and projects building on top of OE-Core, such as Angstrom, Arago
> etc., that are supposed to be part of the Yocto Project as well. See Yocto
> Project branding compliance program for official guidelines, that were
> standardized recently... But the Yocto Project Universe is much larger than
> Poky - there are at least 50 different layers that you can mix and match,
> ranging from different BSPs to different Software stacks...
>
>
>> 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?
>
> Some of that is explained above. I can go into more details offline, if you
> wish.
>
>
>> is that wrong to expect to be able to build a poky image by combining
>> meta-ti and poky.git?
>
> Absolutely not! And I've been building that combination among other things -
> either core-image-minimal or core-image-sato.
>
>
>> > 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?
>
> Depends on which direction you go. Denzil branch is usually considered more
> stable than master, although master is now feature-frozen for stabilization
> before the next release. Unless you start mixing meta-oe and step on to
> systemd issues, as systemd in denzil is not that clean. Anyway, for a simple
> poky+meta-ti combination and images from meta/ directory it should be fine.
>
>
>> my build has restarted fine... i will check the build when they complete.
>
> Let us know. Like I said, I've been building both core-image-minimal and
> core-image-sato w/o problems before.

using denzil branch on both poky.git and meta-ti, i was able to
generate a poky/sato image for beagle. thx.

so what if I want to use poky.git master? is there a meta-ti branch
that works in this case? I think this is what i tried initially (which
triggered that email) which didn't work.


>
> --
> Denys

Re: building yocto images with meta-ti

[Jack Mitchell]

On 20/09/12 08:40, Nicolas Dechesne wrote:
> On Wed, Sep 19, 2012 at 6:26 PM, Denys Dmytriyenko <denys@ti.com> wrote:
>> On Wed, Sep 19, 2012 at 06:04:09PM +0200, Nicolas Dechesne wrote:
>>> hi,
>>>
>>> thanks for your answers
>>>
>>> On Wed, Sep 19, 2012 at 3:57 PM, Denys Dmytriyenko <denys@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 ;-)
>> It is somewhat convoluted, but in general, Poky is a reference distribution
>> and released product built on top of OpenEmbedded-Core. The Yocto Project is
>> an umbrella entity for different projects and initiatives based on the common
>> infrastructure, such as OpenEmbedded-Core, BitBake etc. There are other
>> distributions and projects building on top of OE-Core, such as Angstrom, Arago
>> etc., that are supposed to be part of the Yocto Project as well. See Yocto
>> Project branding compliance program for official guidelines, that were
>> standardized recently... But the Yocto Project Universe is much larger than
>> Poky - there are at least 50 different layers that you can mix and match,
>> ranging from different BSPs to different Software stacks...
>>
>>
>>> 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?
>> Some of that is explained above. I can go into more details offline, if you
>> wish.
>>
>>
>>> is that wrong to expect to be able to build a poky image by combining
>>> meta-ti and poky.git?
>> Absolutely not! And I've been building that combination among other things -
>> either core-image-minimal or core-image-sato.
>>
>>
>>>> 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?
>> Depends on which direction you go. Denzil branch is usually considered more
>> stable than master, although master is now feature-frozen for stabilization
>> before the next release. Unless you start mixing meta-oe and step on to
>> systemd issues, as systemd in denzil is not that clean. Anyway, for a simple
>> poky+meta-ti combination and images from meta/ directory it should be fine.
>>
>>
>>> my build has restarted fine... i will check the build when they complete.
>> Let us know. Like I said, I've been building both core-image-minimal and
>> core-image-sato w/o problems before.
> using denzil branch on both poky.git and meta-ti, i was able to
> generate a poky/sato image for beagle. thx.
>
> so what if I want to use poky.git master? is there a meta-ti branch
> that works in this case? I think this is what i tried initially (which
> triggered that email) which didn't work.
>

As Denys mentions above, on poky master the best thing to do is remove 
the meta-yocto-bsp layer from bblayers.conf in your build directory. 
However, if you wish to build some of the reference yocto machines, in 
the same build directory as you build machines from meta-ti, then 
changing the meta-ti layer priority to be higher than the meta-yocto-bsp 
priority should also fix the issue you're having.

It all stems from the meta-ti layer having a "beagleboard" machine and 
the yocto-bsp-layer also having a "beagleboard" machine.

Regards,


-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--

Re: building yocto images with meta-ti

[Dmytriyenko, Denys]

[-- Attachment #1: Type: text/plain, Size: 5353 bytes --]

I think you missed my explanation - please re-read. I didn't say you should go to denzil, I said you need to update your bblayers.conf

Denys


-----Original Message-----
From: Nicolas Dechesne [ndec13@gmail.com]
Received: Thursday, 20 Sep 2012, 3:41
To: Dmytriyenko, Denys [denys@ti.com]
CC: meta-ti@yoctoproject.org [meta-ti@yoctoproject.org]
Subject: Re: [meta-ti] building yocto images with meta-ti

On Wed, Sep 19, 2012 at 6:26 PM, Denys Dmytriyenko <denys@ti.com> wrote:
> On Wed, Sep 19, 2012 at 06:04:09PM +0200, Nicolas Dechesne wrote:
>> hi,
>>
>> thanks for your answers
>>
>> On Wed, Sep 19, 2012 at 3:57 PM, Denys Dmytriyenko <denys@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 ;-)
>
> It is somewhat convoluted, but in general, Poky is a reference distribution
> and released product built on top of OpenEmbedded-Core. The Yocto Project is
> an umbrella entity for different projects and initiatives based on the common
> infrastructure, such as OpenEmbedded-Core, BitBake etc. There are other
> distributions and projects building on top of OE-Core, such as Angstrom, Arago
> etc., that are supposed to be part of the Yocto Project as well. See Yocto
> Project branding compliance program for official guidelines, that were
> standardized recently... But the Yocto Project Universe is much larger than
> Poky - there are at least 50 different layers that you can mix and match,
> ranging from different BSPs to different Software stacks...
>
>
>> 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?
>
> Some of that is explained above. I can go into more details offline, if you
> wish.
>
>
>> is that wrong to expect to be able to build a poky image by combining
>> meta-ti and poky.git?
>
> Absolutely not! And I've been building that combination among other things -
> either core-image-minimal or core-image-sato.
>
>
>> > 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?
>
> Depends on which direction you go. Denzil branch is usually considered more
> stable than master, although master is now feature-frozen for stabilization
> before the next release. Unless you start mixing meta-oe and step on to
> systemd issues, as systemd in denzil is not that clean. Anyway, for a simple
> poky+meta-ti combination and images from meta/ directory it should be fine.
>
>
>> my build has restarted fine... i will check the build when they complete.
>
> Let us know. Like I said, I've been building both core-image-minimal and
> core-image-sato w/o problems before.

using denzil branch on both poky.git and meta-ti, i was able to
generate a poky/sato image for beagle. thx.

so what if I want to use poky.git master? is there a meta-ti branch
that works in this case? I think this is what i tried initially (which
triggered that email) which didn't work.


>
> --
> Denys

[-- Attachment #2: Type: text/html, Size: 7248 bytes --]

Re: building yocto images with meta-ti

[Nicolas Dechesne]

On Thu, Sep 20, 2012 at 2:22 PM, Dmytriyenko, Denys <denys@ti.com> wrote:
> I think you missed my explanation - please re-read. I didn't say you should
> go to denzil, I said you need to update your bblayers.conf

ok.. thanks. I thought i had tried your suggestions... after a clean
rebuild, it did work.

so, just to make it clear I was able to build -minimal and -sato
images with this config

Build Configuration:
BB_VERSION        = "1.15.3"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "beagleboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.2+snapshot-20120921"
TUNE_FEATURES     = "armv7a vfp neon cortexa9"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto        = "master:df5f9a3e6dfcf8e8f57132843a024b44c0bd90fc"
meta-ti           = "master:7b288d7d05b803032e125f14a3a845c514728003"


>
> Denys
>
>
>
> -----Original Message-----
> From: Nicolas Dechesne [ndec13@gmail.com]
> Received: Thursday, 20 Sep 2012, 3:41
> To: Dmytriyenko, Denys [denys@ti.com]
> CC: meta-ti@yoctoproject.org [meta-ti@yoctoproject.org]
> Subject: Re: [meta-ti] building yocto images with meta-ti
>
> On Wed, Sep 19, 2012 at 6:26 PM, Denys Dmytriyenko <denys@ti.com> wrote:
>> On Wed, Sep 19, 2012 at 06:04:09PM +0200, Nicolas Dechesne wrote:
>>> hi,
>>>
>>> thanks for your answers
>>>
>>> On Wed, Sep 19, 2012 at 3:57 PM, Denys Dmytriyenko <denys@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 ;-)
>>
>> It is somewhat convoluted, but in general, Poky is a reference
>> distribution
>> and released product built on top of OpenEmbedded-Core. The Yocto Project
>> is
>> an umbrella entity for different projects and initiatives based on the
>> common
>> infrastructure, such as OpenEmbedded-Core, BitBake etc. There are other
>> distributions and projects building on top of OE-Core, such as Angstrom,
>> Arago
>> etc., that are supposed to be part of the Yocto Project as well. See Yocto
>> Project branding compliance program for official guidelines, that were
>> standardized recently... But the Yocto Project Universe is much larger
>> than
>> Poky - there are at least 50 different layers that you can mix and match,
>> ranging from different BSPs to different Software stacks...
>>
>>
>>> 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?
>>
>> Some of that is explained above. I can go into more details offline, if
>> you
>> wish.
>>
>>
>>> is that wrong to expect to be able to build a poky image by combining
>>> meta-ti and poky.git?
>>
>> Absolutely not! And I've been building that combination among other things
>> -
>> either core-image-minimal or core-image-sato.
>>
>>
>>> > 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?
>>
>> Depends on which direction you go. Denzil branch is usually considered
>> more
>> stable than master, although master is now feature-frozen for
>> stabilization
>> before the next release. Unless you start mixing meta-oe and step on to
>> systemd issues, as systemd in denzil is not that clean. Anyway, for a
>> simple
>> poky+meta-ti combination and images from meta/ directory it should be
>> fine.
>>
>>
>>> my build has restarted fine... i will check the build when they complete.
>>
>> Let us know. Like I said, I've been building both core-image-minimal and
>> core-image-sato w/o problems before.
>
> using denzil branch on both poky.git and meta-ti, i was able to
> generate a poky/sato image for beagle. thx.
>
> so what if I want to use poky.git master? is there a meta-ti branch
> that works in this case? I think this is what i tried initially (which
> triggered that email) which didn't work.
>
>
>>
>> --
>> Denys

Re: building yocto images with meta-ti

[Koen Kooi]

Op 21 sep. 2012, om 10:44 heeft Nicolas Dechesne <ndec13@gmail.com> het volgende geschreven:

> On Thu, Sep 20, 2012 at 2:22 PM, Dmytriyenko, Denys <denys@ti.com> wrote:
>> I think you missed my explanation - please re-read. I didn't say you should
>> go to denzil, I said you need to update your bblayers.conf
> 
> ok.. thanks. I thought i had tried your suggestions... after a clean
> rebuild, it did work.
> 
> so, just to make it clear I was able to build -minimal and -sato
> images with this config
> 
> Build Configuration:
> BB_VERSION        = "1.15.3"
> TARGET_ARCH       = "arm"
> TARGET_OS         = "linux-gnueabi"
> MACHINE           = "beagleboard"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.2+snapshot-20120921"
> TUNE_FEATURES     = "armv7a vfp neon cortexa9"

A cortex A9 on a beagleboard, wow.

Re: building yocto images with meta-ti

[Nicolas Dechesne]

On Fri, Sep 21, 2012 at 10:49 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> Build Configuration:
>> BB_VERSION        = "1.15.3"
>> TARGET_ARCH       = "arm"
>> TARGET_OS         = "linux-gnueabi"
>> MACHINE           = "beagleboard"
>> DISTRO            = "poky"
>> DISTRO_VERSION    = "1.2+snapshot-20120921"
>> TUNE_FEATURES     = "armv7a vfp neon cortexa9"
>
> A cortex A9 on a beagleboard, wow.

hehe ... yeah, i am doing funky experiments ;-)

i restarted a panda build right after and messed up with my copy/paste ;-)