From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: bbappend - Where should my file be?
Date: Wed, 17 Aug 2011 09:32:08 -0700 [thread overview]
Message-ID: <1313598733.2205.6.camel@scimitar> (raw)
In-Reply-To: <36642C12-5231-4EE6-A267-D469D3E5B98F@keylevel.com>
On Fri, 2011-08-12 at 20:48 +0100, Chris Tapp wrote:
> On 12 Aug 2011, at 13:59, Bruce Ashfield wrote:
>
> >> NOTE: Unpacking
> >> /home/chris/yocto/yocto-downloads/git_git.pokylinux.org.linux-2.6-
> >> windriver.git.tar.gz
> >> to
> >> /home/chris/yocto/sjs-build/tmp/work/LX800-poky-linux/linux-
> >> wrs
> >> -2.6.34
> >> +
> >> git0
> >> +
> >> b67e060194a38c6331da1532bd06446087a42b3b_0
> >> +0431115c9d720fee5bb105f6a7411efb4f851d26-r12/
> >>
> >> NOTE: Unpacking
> >> /home/chris/yocto/meta-keylevel-sjs/recipes/linux/linux-wrs/
> >> defconfig to
> >> /home/chris/yocto/sjs-build/tmp/work/LX800-poky-linux/linux-
> >> wrs
> >> -2.6.34
> >> +
> >> git0
> >> +
> >> b67e060194a38c6331da1532bd06446087a42b3b_0
> >> +0431115c9d720fee5bb105f6a7411efb4f851d26-r12/
> >>
> >
> > That does look right!
>
> What are the rules for naming layers?
>
> I renamed the root for my new layer from 'meta-ebox-3300' to 'meta-
> ebox3300', updated this in bblayers.conf and now my defconf file is
> found as I was expecting...
>
> It seems as if having -<numeric> at the end stops things working.
This sounds like a bug so I filed it here:
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1379
Regards,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-08-17 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 23:51 bbappend - Where should my file be? Chris Tapp
2011-08-11 23:57 ` Scott Garman
2011-08-12 0:28 ` Bruce Ashfield
2011-08-12 8:20 ` Chris Tapp
2011-08-12 12:59 ` Bruce Ashfield
2011-08-12 19:48 ` Chris Tapp
2011-08-17 16:32 ` Joshua Lock [this message]
2011-08-30 18:07 ` Richard Purdie
2011-08-31 19:33 ` Chris Tapp
2011-08-31 20:01 ` 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=1313598733.2205.6.camel@scimitar \
--to=josh@linux.intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.