From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Chris Larson <clarson@kergoth.com>, bitbake-devel@lists.openembedded.org
Subject: Re: bblayers.conf is required?
Date: Tue, 10 Apr 2012 21:14:15 +0100 [thread overview]
Message-ID: <1334088855.10826.36.camel@ted> (raw)
In-Reply-To: <CAMKF1soNohu5iM9j3Sro+MeKPObUsObwzCyFFEsO30cZQ2qJyw@mail.gmail.com>
On Tue, 2012-04-10 at 09:54 -0700, Khem Raj wrote:
> > Yeah, bitbake itself doesn't require bblayers.conf.
>
> right. I forgot about bitbake's life without OE :)
Its a backwards compatibility thing. When we implemented bblayers.conf
we left it backwards compatible with what went before. It will work if
BBPATH is set such that it can find a conf/bitbake.conf .
Cheers,
Richard
prev parent reply other threads:[~2012-04-10 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 13:03 bblayers.conf is required? Gary Thomas
2012-04-09 18:07 ` Khem Raj
2012-04-10 16:09 ` Jeremy Puhlman
2012-04-10 16:31 ` Chris Larson
2012-04-10 16:54 ` Khem Raj
2012-04-10 20:14 ` 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=1334088855.10826.36.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
--cc=raj.khem@gmail.com \
/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