From: Gary Thomas <gary@mlbassoc.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Conf notes
Date: Mon, 24 Feb 2014 06:50:32 -0700 [thread overview]
Message-ID: <530B4E28.1070308@mlbassoc.com> (raw)
In-Reply-To: <CAP71Wjx=6Ux7CWmr4FJcLPyp0xah3jFO=7v6izNi2dfNNcWWYQ@mail.gmail.com>
On 2014-02-24 06:40, Nicolas Dechesne wrote:
> On Mon, Feb 24, 2014 at 2:15 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> I just tried this with the latest master and it is only looking in
>> the meta-yocto layer even though there is a conf-notes.txt in one of
>> my local layers as well.
>
> hmm. i just tried too. i create meta-layer with:
>
> $ find meta-mylayer/
> meta-mylayer/
> meta-mylayer/conf
> meta-mylayer/conf/conf-notes.txt
> meta-mylayer/conf/bblayers.conf.sample
> meta-mylayer/conf/layer.conf
> meta-mylayer/conf/local.conf.sample
> meta-mylayer/conf/site.conf.sample
>
> then, if I run
>
> $ TEMPLATECONF=meta-mylayer/conf . oe-init-build-env bbb
>
> It is working fine:
Indeed, that does work, but only for the first time of if you specify TEMPLATECONF.
I often have build trees that live for a very long time (think months) and I'll
do something like this:
TEMPLATECONF=my-layer/conf . ${POKY}/oe-init-build-env <somedir>
then later, e.g. after a reboot of my build host, I do just this:
. ${POKY}/oe-init-build-env <somedir>
This renews the build setting for that setup just fine, but in this case, I'll
get the default "conf-notes.txt", not my layer specific ones.
>
> ### Shell environment set up for builds. ###
>
> You can now run 'bitbake <target>'
>
> Common targets are:
> my-custom-image
>
> You can also run generated qemu images with a command like 'runqemu qemux86'
>
> I tried with up-to-date poky, e.g.
>
> commit a1faa7df2a0972fa631d3aee98c59f6b0e8eb43c
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date: Mon Feb 24 12:57:38 2014 +0000
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-02-24 13:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 19:06 Conf notes Laszlo Papp
2014-02-24 6:34 ` Nicolas Dechesne
2014-02-24 9:35 ` Laszlo Papp
2014-02-24 10:28 ` Nicolas Dechesne
2014-02-24 11:47 ` Laszlo Papp
2014-02-24 12:49 ` Nicolas Dechesne
2014-02-24 13:03 ` Laszlo Papp
2014-02-24 13:15 ` Gary Thomas
2014-02-24 13:40 ` Nicolas Dechesne
2014-02-24 13:50 ` Gary Thomas [this message]
2014-02-24 14:13 ` Nicolas Dechesne
2014-02-24 14:09 ` Laszlo Papp
2014-02-24 14:13 ` Nicolas Dechesne
2014-02-24 14:30 ` Laszlo Papp
2014-02-24 18:27 ` Laszlo Papp
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=530B4E28.1070308@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=nicolas.dechesne@linaro.org \
--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