From: "Robert P. J. Day" <firstname.lastname@example.org>
To: Quentin Schulz <email@example.com>
Cc: YP docs mailing list <firstname.lastname@example.org>
Subject: Re: [docs] Description of BBPATH in BB user manual seems ... wrong
Date: Mon, 15 Mar 2021 16:19:02 -0400 (EDT) [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
On Mon, 15 Mar 2021, Quentin Schulz wrote:
> Hi Robert,
> On Mon, Mar 15, 2021 at 09:05:53AM -0400, Robert P. J. Day wrote:
> > Section 3.4.1 of BB manual:
> > https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html#locating-include-and-class-files
> > "BitBake uses the BBPATH variable to locate needed include and class
> > files. Additionally, BitBake searches the current directory for
> > include and require directives.
> > ... snip ..
> > "In order for include and class files to be found by BitBake, they
> > need to be located in a “classes” subdirectory that can be found in
> > BBPATH."
> > first, is BBPATH not used for finding conf files as well? and the
> Yes it is.
> > wording of that second paragraph suggests that include files need to
> > be in a classes subdirectory to be found, which i'm pretty sure isn't
> > true.
> I think what was meant by "include" files are conf files.... which
> (probably) technically are include files to Yocto PoV.
> Not entirely sure but I think Yocto includes all appropriate conf files
> to create the "base" "environment" of all recipes.
> basically, stuff on top of bitbake.conf and what is the environment
> being reset to between tasks/recipes.
> Those are guesses though.
well, i think that wording in the BB user manual is at least a
little misleading, but if others think it's sufficiently clear, i'll
shut up about it.
next prev parent reply other threads:[~2021-03-15 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 13:05 Description of BBPATH in BB user manual seems ... wrong Robert P. J. Day
2021-03-15 13:10 ` [docs] " Quentin Schulz
2021-03-15 20:19 ` Robert P. J. Day [this message]
2021-03-16 9:01 ` Quentin Schulz
2021-03-16 9:58 ` Robert P. J. Day
2021-03-17 9:19 ` Robert P. J. Day
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.