From: Erik Burghardt <erik.burghardt@kiwigrid.com>
To: docs@lists.yoctoproject.org
Subject: Wrong documentation about BBLAYERS?
Date: Fri, 23 Feb 2024 13:12:42 +0100 [thread overview]
Message-ID: <CAE=EZ9y6s=x3X7nbp-QCysJZ0Uc=RjpdrwKzCAAWih_toySf4Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2249 bytes --]
Dear all,
I'm a beginner in terms of working with the Yocto Project.
As far as I see it, one huge feature of the Yocto Project is how layers
override each other. Even though I think everyone will agree with that, how
this works is not prominently featured in the documentation and not
obvious. That is why I wanted to provide a patch for
https://docs.yoctoproject.org/ref-manual/variables.html#term-BBLAYERS,
clarifying that layers that are on the top in the BBLAYERS override layers
that are beyond them (when BBFILE_PRIORITY is the same).
Before I wrote the patch, I searched the entire documentation for mentions
of BBLAYERS and found the following in
https://docs.yoctoproject.org/bsp-guide/bsp.html#bsp-layers:
"NOTE: Ordering and BBFILE_PRIORITY for the layers listed in BBLAYERS
matter. For example, if multiple layers define a machine configuration, the
OpenEmbedded build system uses the last layer searched given similar layer
priorities. The build system works from the top-down through the layers
listed in BBLAYERS."
That was confusing for me, because as far as I read this note, BBLAYERS
works like this:
BBLAYERS ?= " \
${TOPDIR}/../sources/poky/meta \
${TOPDIR}/../sources/poky/meta-poky \"
A distro.conf in "meta-poky" will override a distro.conf in "meta". What I
experience in my project though, is that it is the other way around. Now I
don't know if the documentation needs a change, if I'm reading the
documentation wrong or if there is some kind of bug in my build.
I would love to hear your thoughts, thank you
Erik
--
*Erik Burghardt*
Embedded Software Engineer
Kiwigrid GmbH | Kleiststraße 10 a – c | 01129 Dresden | Germany
*erik.burghardt@kiwigrid.com <erik.burghardt@kiwigrid.com>* | *www.kiwigrid.com
<http://www.kiwigrid.com/>* | *Kiwigrid bei LinkedIn
<https://www.linkedin.com/company/kiwigrid-gmbh>*
Registered Office/Sitz der Gesellschaft: Dresden Registered
Court/Registergericht: Amtsgericht Dresden | HRB 30058
Chairman of the Advisory Board/Beiratsvorsitzender: Hans-Peter Villis
Managing Directors/Geschäftsführer: Dr. Frank Schlichting (Chief Executive
Officer), Janek Schuffenhauer (Chief Financial Officer), Matthias Popella
(Prokurist)
[-- Attachment #2: Type: text/html, Size: 4096 bytes --]
next reply other threads:[~2024-02-23 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 12:12 Erik Burghardt [this message]
2024-02-23 12:22 ` [docs] Wrong documentation about BBLAYERS? Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE=EZ9y6s=x3X7nbp-QCysJZ0Uc=RjpdrwKzCAAWih_toySf4Q@mail.gmail.com' \
--to=erik.burghardt@kiwigrid.com \
--cc=docs@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).