From: Jeremy Puhlman <jpuhlman@mvista.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: bblayers.conf is required?
Date: Tue, 10 Apr 2012 09:09:36 -0700 [thread overview]
Message-ID: <4F845B40.2040302@mvista.com> (raw)
In-Reply-To: <CAMKF1sr5t8DptrHBO6NdA0mh2URs6QVXgpfLSXMcFHW9ybX3jg@mail.gmail.com>
On 4/9/2012 11:07 AM, Khem Raj wrote:
> On Mon, Apr 9, 2012 at 6:03 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>> The config file conf/bblayers.conf seems to be required:
>> $ bitbake core-image-minimal
>> Unable to find conf/bblayers.conf
>> BitBake must be run from within your build directory: /home/local/p60_poky
>>
>> but the bitbake documentation says otherwise:
>> <para>BitBake will first search the current working directory
>> for an optional "conf/bblayers.conf" configuration file. This file is
>> expected to contain a BBLAYERS variable which is a space delimited list of
>> 'layer' directories. For each directory in this list, a "conf/layer.conf"
>> file will be searched for and parsed with the LAYERDIR variable being set to
>> the directory where the layer was found. The idea is these files will setup
>> BBPATH and other variables correctly for a given build directory
>> automatically for the user.</para>
>>
>> Maybe the documentation should just read "required" instead of "optional"?
>
> I think yes. Next action is a patch or bug report.
Hmmm you used to be able to run bitbake by just setting the BBPATH
variable in the environment, and not need a bblayers file. It is not the
suggested use case anymore, but looking at cooker I don't see anything
in there in the layer handling code that would preclude that use.
Also that final error message comes from the content bitbake script not
bitbake proper.
--
Jeremy Puhlman
Montavista Software, LLC.
next prev parent reply other threads:[~2012-04-10 16:19 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 [this message]
2012-04-10 16:31 ` Chris Larson
2012-04-10 16:54 ` Khem Raj
2012-04-10 20:14 ` 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=4F845B40.2040302@mvista.com \
--to=jpuhlman@mvista.com \
--cc=bitbake-devel@lists.openembedded.org \
--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