From: Darren Hart <dvhart@linux.intel.com>
To: 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 08:55:47 -0700 [thread overview]
Message-ID: <4F636283.7040800@linux.intel.com> (raw)
In-Reply-To: <4F635D37.2020406@linux.intel.com>
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.
--
Darren
>
> --
> Darren
>
> On 03/15/2012 03:00 PM, Darren Hart wrote:
>> Fixes [YOCTO #2114]
>>
>> The rt-tests recipe was issuing the following WARNINGs:
>>
>> WARNING: For recipe rt-tests, the following files/directories were installed
>> but not shipped in any package:
>> WARNING: /usr/src
>> WARNING: /usr/src/backfire
>> WARNING: /usr/src/backfire/backfire.c
>> WARNING: /usr/src/backfire/Makefile
>>
>> Add ${prefix}/src/backfire to FILES_${PN} to include these files in the package.
>> These depend on the target kernel and are meant to be able to be rebuilt as
>> needed. Ideally we would also build this module and include it with rt-tests or
>> the linux-yocto-rt kernel. For now, conform with the intent of the rt-tests
>> Makefile and avoid the WARNINGs.
>>
>> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
>> ---
>> meta/recipes-rt/rt-tests/rt-tests_0.83.bb | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/meta/recipes-rt/rt-tests/rt-tests_0.83.bb b/meta/recipes-rt/rt-tests/rt-tests_0.83.bb
>> index 78d51b3..6425027 100644
>> --- a/meta/recipes-rt/rt-tests/rt-tests_0.83.bb
>> +++ b/meta/recipes-rt/rt-tests/rt-tests_0.83.bb
>> @@ -11,6 +11,7 @@ SRCREV = "5f1e84f8b015df3ff950056494134eca3f640d70"
>>
>> # git -> 0.83 needs a PE bump
>> PE = "1"
>> +PR = "r1"
>>
>> SRC_URI = "git://github.com/clrkwllms/rt-tests.git"
>>
>> @@ -25,3 +26,5 @@ do_install() {
>> oe_runmake install DESTDIR=${D} SBINDIR=${sbindir} MANDIR=${mandir} \
>> INCLUDEDIR=${includedir}
>> }
>> +
>> +FILES_${PN} += "${prefix}/src/backfire"
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-03-16 16:05 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 [this message]
2012-03-16 16:26 ` Richard Purdie
2012-03-16 16:28 ` Darren Hart
2012-03-16 17:11 ` Richard Purdie
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=4F636283.7040800@linux.intel.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox