From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org
Subject: Re: bbappend - Where should my file be?
Date: Fri, 12 Aug 2011 08:59:02 -0400 [thread overview]
Message-ID: <4E452396.1070506@windriver.com> (raw)
In-Reply-To: <B44F0C76-F163-4264-B052-BA9E4CC4CDC3@keylevel.com>
On 11-08-12 04:20 AM, Chris Tapp wrote:
> Scott / Bruce,
>
>
> On 12 Aug 2011, at 00:57, Scott Garman wrote:
>
>>
>>> cp: cannot stat
>>> `/home/chris/yocto/yocto-versions/laverne-4.0.1/meta/recipes-kernel/linux/files/defconfig':
>>>
>>> No such file or directory
>>
>> It looks like this is where the file is expected.
>>
>> I believe also meta/recipes-kernel/linux/linux/defconfig should also
>> work.
>
> I should have mentioned that ;-) As the bbappend file is in my layer, I
> was expecting (and want) the defconfig file to be stored/found in it. I
> created this layer by copying another one that I've got. It's unpack log
> shows:
hah. For some reason that flew right over my head. Must be
the 500 email I read a day :)
>
> 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!
>
> I suspect I've got something configured wrong with the new layer, but...
>
> On 12 Aug 2011, at 01:28, Bruce Ashfield wrote:
>
>>> I believe also meta/recipes-kernel/linux/linux/defconfig should also
>>> work.
>>
>> Yep, bitbake is telling us where it is looking. The -wrs_git is the
>> extension to the recipe, so that isn't where it is looking.
>
> Sorry Bruce, that was a typo (see working log above for a layer that
> works). I've tried using:
>
> MyLayer/recipies/linux/defconfig
> MyLayer/recipies/linux/files/defconfig (with no FILESEXTRAPATHS)
> MyLayer/recipies/linux/linux-wrs/defconfig
>
>> On another note, there's been a lot of fixes to the kern tools to
>> improve the process for adding BSPs and extending the tree (and
>> one defconfig bug fix), so I'll be interested to hear how this
>> goes.
>
> I'm planning to give it a try after the next release. I'm currently just
> trying to migrate an existing (4.0.1) project to a new platform and
> decided to add a new layer rather than change version at the same time.
Sounds good.
Bruce
>
> Chris Tapp
>
> opensource@keylevel.com
> www.keylevel.com
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2011-08-12 12:59 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 [this message]
2011-08-12 19:48 ` Chris Tapp
2011-08-17 16:32 ` Joshua Lock
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=4E452396.1070506@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=opensource@keylevel.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.