From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: if a layer doesn't provide any conf/ or classes/ files, any need for BBPATH?
Date: Wed, 23 Jul 2014 17:12:42 +0100 [thread overview]
Message-ID: <1406131962.22985.127.camel@ted> (raw)
In-Reply-To: <alpine.LFD.2.11.1407222018550.25203@localhost>
On Tue, 2014-07-22 at 20:21 -0400, Robert P. J. Day wrote:
> 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?
It doesn't need to, no. Convention is to leave it around to make it easy
to add them later since it doesn't hurt much either.
Cheers,
Richard
prev parent reply other threads:[~2014-07-23 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 0:21 if a layer doesn't provide any conf/ or classes/ files, any need for BBPATH? Robert P. J. Day
2014-07-23 16:12 ` Richard Purdie [this message]
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=1406131962.22985.127.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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