From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Conf notes
Date: Mon, 24 Feb 2014 06:15:53 -0700 [thread overview]
Message-ID: <530B4609.7070307@mlbassoc.com> (raw)
In-Reply-To: <CAP71WjxHc6+9DDGeQsuAc3Cv7qN+bfPgNT-ju01z6pje3Q2qEg@mail.gmail.com>
On 2014-02-24 05:49, Nicolas Dechesne wrote:
> On Mon, Feb 24, 2014 at 12:47 PM, Laszlo Papp <lpapp@kde.org> wrote:
>>> hmm. do you get any error message?
>>
>> Nope, I have been using this construction for several weeks now. The
>> local and bblayer samples have been extracted properly into the build
>> folder, so in that sense, there is no infrastructural change
>> introduced in here, just yet another file added in the folder.
>
> well, i don't see what can possibly go wrong then... especially if
> layers.conf.sample and bblayer sample files work fine... maybe adding
> "set -x" in the script would reveal something..
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.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-02-24 13:15 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 [this message]
2014-02-24 13:40 ` Nicolas Dechesne
2014-02-24 13:50 ` Gary Thomas
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=530B4609.7070307@mlbassoc.com \
--to=gary@mlbassoc.com \
--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