From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Scott Garman <scott.a.garman@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: bbappend - Where should my file be?
Date: Thu, 11 Aug 2011 20:28:20 -0400 [thread overview]
Message-ID: <4E4473A4.4060403@windriver.com> (raw)
In-Reply-To: <4E446C74.9070807@intel.com>
On 11-08-11 7:57 PM, Scott Garman wrote:
> On 08/11/2011 04:51 PM, Chris Tapp wrote:
>> I've got a linux-wrs_git.bbappend file in a layer (under poky laverne
>> 4.0.1) that contains:
>>
>> COMPATIBLE_MACHINE_Vortex86DX = "Vortex86DX"
>> WRMACHINE_Vortex86DX = "common_pc"
>>
>> FILESEXTRAPATHS := "${THISDIR}/${PN}"
>>
>> SRC_URI += " file://defconfig"
>>
>> Where should the defconfig file be relative to the bbappend?
>>
>> I've tried:
>>
>> MyLayer
>> +--- recipies
>> +--- linux
>> +--- linux-wrs_git.bbappend
>> +--- linux-wrs_git
>> +--- defconfig
>>
>>
>> However, my defconfig file isn't being picked up during do_unpack:
>>
>> 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.
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.
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.
Bruce
>
> Scott
>
next prev parent reply other threads:[~2011-08-12 0:28 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 [this message]
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
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=4E4473A4.4060403@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=scott.a.garman@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.