From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jack Mitchell <ml@communistcode.co.uk>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: local.conf & bblayers.conf changes...
Date: Tue, 03 Jul 2012 20:22:28 +0100 [thread overview]
Message-ID: <2056870.tdrijsDPYL@helios> (raw)
In-Reply-To: <4FF32E93.9050802@communistcode.co.uk>
On Tuesday 03 July 2012 18:40:35 Jack Mitchell wrote:
> What I did was create a new build directory and do a diff between my
> current config and the newly generated config.
>
> I couldn't find the reference local.conf file that bitbake tells you to
> compare against...
It's in meta(-yocto)/conf/local.conf.sample.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-07-03 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 16:42 local.conf & bblayers.conf changes Rich Pixley
2012-07-03 17:01 ` Saul Wold
2012-07-03 17:19 ` Rich Pixley
2012-07-03 17:35 ` Mark Hatle
2012-07-03 17:47 ` Martin Jansa
2012-07-03 17:51 ` Mark Hatle
2012-07-03 18:00 ` Martin Jansa
2012-07-03 19:20 ` Paul Eggleton
2012-07-03 17:22 ` Martin Jansa
2012-07-03 17:40 ` Jack Mitchell
2012-07-03 19:22 ` Paul Eggleton [this message]
2012-07-04 8:29 ` Jack Mitchell
2012-07-04 8:32 ` Jack Mitchell
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=2056870.tdrijsDPYL@helios \
--to=paul.eggleton@linux.intel.com \
--cc=ml@communistcode.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox