From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: if a layer doesn't provide any conf/ or classes/ files, any need for BBPATH?
Date: Tue, 22 Jul 2014 20:21:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407222018550.25203@localhost> (raw)
i just noticed that the meta-oe/meta-filesystems layer provides no
(additional) conf/ files or classes/ files. so in a case like that, is
there any need to add that layer info to BBPATH in its layer.conf
file?
conversely, if a layer contains no .bb or .bbappend files, does it
need to be included in BBFILES?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2014-07-23 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 0:21 Robert P. J. Day [this message]
2014-07-23 16:12 ` if a layer doesn't provide any conf/ or classes/ files, any need for BBPATH? Richard Purdie
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=alpine.LFD.2.11.1407222018550.25203@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.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 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.