From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] rt-tests: Add src/backfire to FILES_${PN}
Date: Fri, 16 Mar 2012 17:11:02 +0000 [thread overview]
Message-ID: <1331917862.18586.210.camel@ted> (raw)
In-Reply-To: <4F636A2E.2090404@linux.intel.com>
On Fri, 2012-03-16 at 09:28 -0700, Darren Hart wrote:
>
> On 03/16/2012 09:26 AM, Richard Purdie wrote:
> > On Fri, 2012-03-16 at 08:55 -0700, Darren Hart wrote:
> >> On 03/16/2012 08:33 AM, Darren Hart wrote:
> >>> Hrm, this silences the warnings, but the backfire sources are not
> >>> installed on the rootfs....
> >>>
> >>> Anyone see what is wrong with the below? Is there some magic that purges
> >>> /usr/src in a minimal build?
> >>
> >> I was adding "/usr/src/backfire" to FILES_${PN}. It seems one should add
> >> "/usr/src/backfire/*" to actually get the files.
> >>
> >> However, I am surprised that the warnings went away and the files were
> >> still not packaged when I used "/usr/src/backfire". Is this expected
> >> behavior?
> >>
> >> I have pushed the new version to the same branch using
> >> "/usr/src/backfire/*". Built,booted,and verified on qemux86 using
> >> core-image-rt.
> >
> > FWIW with your original patch I'm seeing things being correctly packaged
> > in the main package (rt-tests) which is consistent with the warning
> > message being fixed.
>
> I see them appear in the rt-tests "package" dir, but not in the rootfs
> unless I append the "/*".
If I view the contents of the rt-tests*.rpm in deploy/rpm/xxx/, I can
see the files listed. This is with current master.
Please check what you tested ;-)
Cheers,
Richard
next prev parent reply other threads:[~2012-03-16 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 22:00 [PATCH 0/1] rt-tests: Add src/backfire to FILES_${PN} Darren Hart
2012-03-15 22:00 ` [PATCH 1/1] " Darren Hart
2012-03-16 15:33 ` Darren Hart
2012-03-16 15:55 ` Darren Hart
2012-03-16 16:26 ` Richard Purdie
2012-03-16 16:28 ` Darren Hart
2012-03-16 17:11 ` Richard Purdie [this message]
2012-03-16 17:59 ` Darren Hart
2012-03-16 16:06 ` Saul Wold
2012-03-16 16:16 ` Darren Hart
2012-03-16 16:24 ` Richard Purdie
2012-03-16 3:35 ` [PATCH 0/1] " Saul Wold
2012-03-16 5:32 ` 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=1331917862.18586.210.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.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 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.