From: Saul Wold <sgw@linux.intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: New recipes not installing in core-image-minimal
Date: Thu, 26 Jan 2012 17:42:29 -0800 [thread overview]
Message-ID: <4F220105.3080600@linux.intel.com> (raw)
In-Reply-To: <4F21FDEF.2010500@linux.intel.com>
On 01/26/2012 05:29 PM, Darren Hart wrote:
> In support of a new BSP I've written two new recipes and appended to
> another to depend on them. The new recipes files are not appearing in
> the resulting images. I'm sure I'm overlooking something trivial, but
> I'm not sure what it would be. The layer is available here:
>
> http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=dvhart/sys940x
>
> I've added ranpwd, genmac, and appended to netbase.
>
> netbase RDEPENDS on genmac and genmac RDEPENDS on ranpwd. Building
> core-image-minimal triggers the build of genmac and ranpwd, and the
> modified /etc/network/interfaces appears in the rootfs. genmac and
> ranpwd place the appropriate files in their workdir/image directory, but
> those files don't make it into the rootfs.
>
RDEPENDS_${PN} would work much better !
Sau!
> Can anyone offer an explanation as to why that might be? The top 4
> commits of the repository linked to above will list the new recipes and
> the bbappend for reference.
>
> Thanks,
>
next prev parent reply other threads:[~2012-01-27 1:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 1:29 New recipes not installing in core-image-minimal Darren Hart
2012-01-27 1:42 ` Saul Wold [this message]
2012-01-27 1:57 ` Darren Hart
2012-01-27 8:08 ` Martin Jansa
2012-01-27 10:22 ` Joshua Immanuel
2012-01-27 10:30 ` Martin Jansa
2012-01-27 17:13 ` Darren Hart
2012-01-30 11:02 ` Joshua Immanuel
2012-01-27 8:02 ` Martin Jansa
2012-01-27 8:06 ` Darren Hart
2012-01-31 18:21 ` Darren Hart
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=4F220105.3080600@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=dvhart@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.