Skip to contentSkip to conversation

clarification about BSP layer names and bblayers.conf file?

DISCUSSION Robert P. J. Day 3 participants 6 messages Apr 19, 2013 – Apr 22, 2013

lore
Share & tools
lore
#0 lore raw

from section 1.1 of BSP developers guide:

http://www.yoctoproject.org/docs/latest/bsp-guide/bsp-guide.html#bsp-layers

first, it's not actually *required* that a layer name start with the prefix "meta-", is it? pretty sure it's not and, if it isn't, that should be made abundantly clear. it's fine to point out that it's a well-established convention but it should still be mentioned explicitly that it's not necessary.

second, the BBLAYERS example there seems overly complicated and
potentially confusing to beginners. the fact that meta-yocto is listed as NON_REMOVABLE might make readers wonder how they're supposed to know that. why not go with something a lot more people will see, like, say:

     BBLAYERS = ?" \                  <-- and that looks like a typo
       /usr/local/src/yocto/meta \
       /usr/local/src/yocto/meta-ti \
       "

     BBLAYERS_NON_REMOVABLE ?= " \
       /usr/local/src/yocto/meta \
       "

finally, the passing reference to layers that contain sub-BSP-layers
is good, but show an example, such as the fact that the meta-crownbay layer.conf file has a dependency on meta-intel:

...
LAYERDEPENDS_crownbay = "intel"

never pass up the opportunity to reinforce an idea with a few lines
of actual code. :-)

more shortly ...

rday

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
#1 lore raw
Quoted 5 lines · Robert P. J. Day

first, it's not actually *required* that a layer name start with the prefix "meta-", is it? pretty sure it's not and, if it isn't, that should be made abundantly clear. it's fine to point out that it's a well-established convention but it should still be mentioned explicitly that it's not necessary.

If we agree that what we currently have is "version 1", and in-line with the philosophy of always throwing away "version 1", my gut feeling is that instead of poky being the base of everything and everything else added on top as layers, I believe the people running this project would start with openembedded-core as the base, with poky being simply one (of many) layers on top and therefore (properly) renamed to meta-poky. My point is that in an ideal world poky should be renamed, to follow the accepted convention; but since it isn't, it demonstrates that layers don't have to start with the "meta-*" prefix.

Quoted 5 lines

the fact that meta-yocto is listed
as NON_REMOVABLE might make readers wonder how they're supposed to know that. why not go with something a lot more people will see, like, say:

Quoted 8 lines
     BBLAYERS = ?" \                  <-- and that looks like a typo
       /usr/local/src/yocto/meta \
       /usr/local/src/yocto/meta-ti \
       "

     BBLAYERS_NON_REMOVABLE ?= " \
       /usr/local/src/yocto/meta \
       "

The whole concept of "non-removable" layers seems redundant. If a person were trying to build an image for i.MX53 that makes use of TI's work, the meta-ti layer would be just as "non-removable" as any other, wouldn't it?

#2 lore raw
In reply to Robert P. J. Day
Quoted 10 lines · Robert P. J. Day

from section 1.1 of BSP developers guide:

http://www.yoctoproject.org/docs/latest/bsp-guide/bsp-guide.html#bsp-layers

first, it's not actually *required* that a layer name start with the prefix "meta-", is it? pretty sure it's not and, if it isn't, that should be made abundantly clear. it's fine to point out that it's a well-established convention but it should still be mentioned explicitly that it's not necessary.

Right, the naming isn't required and it would make sense to make that clear, I agree.

Quoted 6 lines

second, the BBLAYERS example there seems overly complicated and
potentially confusing to beginners. the fact that meta-yocto is listed as NON_REMOVABLE might make readers wonder how they're supposed to know that. why not go with something a lot more people will see, like, say:

Quoted 9 lines
     BBLAYERS = ?" \                  <-- and that looks like a typo
       /usr/local/src/yocto/meta \
       /usr/local/src/yocto/meta-ti \
       "

     BBLAYERS_NON_REMOVABLE ?= " \
       /usr/local/src/yocto/meta \
       "

I agree - the whole NON_REMOVABLE thing doesn't add anything and should be removed - the example is just trying to show how to add a BSP layer - the rest just adds potential confusion. And, yeah, it's a typo..

Quoted 10 lines

finally, the passing reference to layers that contain sub-BSP-layers
is good, but show an example, such as the fact that the meta-crownbay layer.conf file has a dependency on meta-intel:

...
LAYERDEPENDS_crownbay = "intel"

never pass up the opportunity to reinforce an idea with a few lines
of actual code. :-)

Agreed, but on the other hand we don't really want to be too intel-specific (I know, we have crownbay everywhere else, but anyway..)

Tom

Quoted 4 lines

more shortly ...

rday

#3 lore raw
Quoted 13 lines · Tom Zanussi
Quoted 11 lines · Robert P. J. Day

second, the BBLAYERS example there seems overly complicated and
potentially confusing to beginners. the fact that meta-yocto is listed as NON_REMOVABLE might make readers wonder how they're supposed to know that. why not go with something a lot more people will see, like, say:

     BBLAYERS = ?" \                  <-- and that looks like a typo
       /usr/local/src/yocto/meta \
       /usr/local/src/yocto/meta-ti \
       "
Quoted 8 lines
Quoted 4 lines
     BBLAYERS_NON_REMOVABLE ?= " \
       /usr/local/src/yocto/meta \
       "

I agree - the whole NON_REMOVABLE thing doesn't add anything and should be removed - the example is just trying to show how to add a BSP layer - the rest just adds potential confusion. And, yeah, it's a typo..

i'll let someone else decide what to do there.

Quoted 7 lines
Quoted 7 lines

finally, the passing reference to layers that contain sub-BSP-layers
is good, but show an example, such as the fact that the meta-crownbay layer.conf file has a dependency on meta-intel:

...
LAYERDEPENDS_crownbay = "intel"

Quoted 6 lines
Quoted 3 lines

never pass up the opportunity to reinforce an idea with a few lines
of actual code. :-)

Agreed, but on the other hand we don't really want to be too intel-specific (I know, we have crownbay everywhere else, but anyway..)

i was just looking for an example of the kind of hierarchical layer
structure you find in meta-intel. is there another layer that has that kind of structure?

rday

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
#4 lore raw
Quoted 37 lines · Robert P. J. Day
Quoted 13 lines · Tom Zanussi
Quoted 11 lines · Robert P. J. Day

second, the BBLAYERS example there seems overly complicated and
potentially confusing to beginners. the fact that meta-yocto is listed as NON_REMOVABLE might make readers wonder how they're supposed to know that. why not go with something a lot more people will see, like, say:

     BBLAYERS = ?" \                  <-- and that looks like a typo
       /usr/local/src/yocto/meta \
       /usr/local/src/yocto/meta-ti \
       "
Quoted 8 lines
Quoted 4 lines
     BBLAYERS_NON_REMOVABLE ?= " \
       /usr/local/src/yocto/meta \
       "

I agree - the whole NON_REMOVABLE thing doesn't add anything and should be removed - the example is just trying to show how to add a BSP layer - the rest just adds potential confusion. And, yeah, it's a typo..

i'll let someone else decide what to do there.

Quoted 11 lines
Quoted 10 lines

finally, the passing reference to layers that contain sub-BSP-layers
is good, but show an example, such as the fact that the meta-crownbay layer.conf file has a dependency on meta-intel:

...
LAYERDEPENDS_crownbay = "intel"

never pass up the opportunity to reinforce an idea with a few lines
of actual code. :-)

Quoted 7 lines
Quoted 2 lines

Agreed, but on the other hand we don't really want to be too intel-specific (I know, we have crownbay everywhere else, but anyway..)

i was just looking for an example of the kind of hierarchical layer
structure you find in meta-intel. is there another layer that has that kind of structure?

A quick scan of all the layers I have opengrokked here doesn't show any either, so possibly meta-intel is currently the only example. If so, let's use it..

Tom

Quoted 2 lines

rday

#5 lore raw
Quoted 10 lines · Tom Zanussi
Quoted 4 lines · Robert P. J. Day

i was just looking for an example of the kind of hierarchical
layer structure you find in meta-intel. is there another layer that has that kind of structure?

A quick scan of all the layers I have opengrokked here doesn't show any either, so possibly meta-intel is currently the only example. If so, let's use it..

as a recap, for the purposes of my oe/yocto course, i was after a
range of BSP definitions from simplest to most complex. at one end, the example i picked on as a layer that defined a single variation of a single board was raspberry-pi.

from there, i can demonstrate examples of, say, a layer that defines
more than one variant of a single machine (say, meta-intel's meta-crownbay), then a layer that defines a number of independent machines (say, meta-yocto-bsp), up to the hierarchical structure of meta-intel, and any other interesting variations i run across in between.

rday

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================