From: Chong Lu <Chong.Lu@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] perf: split package
Date: Thu, 17 Jul 2014 09:43:22 +0800 [thread overview]
Message-ID: <53C72A3A.50101@windriver.com> (raw)
In-Reply-To: <CADkTA4MMphKfFSKw5ViEBgYn+fFJbABeO1hZg+cs4j0eqr__Jw@mail.gmail.com>
On 07/16/2014 09:04 PM, Bruce Ashfield wrote:
> On Wed, Jul 16, 2014 at 4:00 AM, Chong Lu <Chong.Lu@windriver.com> wrote:
>> Fix incorrect paths to split perf package.
> Can you elaborate here ? This commit message doesn't really tell us much.
> Why is the current split incorrect ? What is the symptom and result of the
> incorrect split ? Are the package contents the same after this change ?
>
> Bruce
Hi Bruce,
Currently, perf can't split to perf-archive, perf-tests, perf-python and
perf-perl.
All files are included in perf package. For example, like perf-tests
package:
It generates files in '${exec_prefix}/libexec/perf-core/tests', not in
'${libdir}/perf/perf-core/tests'.
So I change the files paths to make split successfully.
I will improve commit message and resend a V2.
Best Regards
Chong
>> Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
>> ---
>> meta/recipes-kernel/perf/perf.bb | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/meta/recipes-kernel/perf/perf.bb b/meta/recipes-kernel/perf/perf.bb
>> index 20968f9..781a738 100644
>> --- a/meta/recipes-kernel/perf/perf.bb
>> +++ b/meta/recipes-kernel/perf/perf.bb
>> @@ -166,10 +166,10 @@ RSUGGESTS_${PN} += "${PN}-archive ${PN}-tests ${RSUGGESTS_SCRIPTING}"
>>
>> FILES_${PN} += "${libexecdir}/perf-core ${exec_prefix}/libexec/perf-core ${libdir}/traceevent"
>> FILES_${PN}-dbg += "${libdir}/python*/site-packages/.debug"
>> -FILES_${PN}-archive = "${libdir}/perf/perf-core/perf-archive"
>> -FILES_${PN}-tests = "${libdir}/perf/perf-core/tests"
>> -FILES_${PN}-python = "${libdir}/python*/site-packages ${libdir}/perf/perf-core/scripts/python"
>> -FILES_${PN}-perl = "${libdir}/perf/perf-core/scripts/perl"
>> +FILES_${PN}-archive = "${exec_prefix}/libexec/perf-core/perf-archive"
>> +FILES_${PN}-tests = "${exec_prefix}/libexec/perf-core/tests"
>> +FILES_${PN}-python = "${libdir}/python*/site-packages ${exec_prefix}/libexec/perf-core/scripts/python"
>> +FILES_${PN}-perl = "${exec_prefix}/libexec/perf-core/scripts/perl"
>>
>>
>> INHIBIT_PACKAGE_DEBUG_SPLIT="1"
>> --
>> 1.9.1
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2014-07-17 1:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 8:00 [PATCH 0/1] perf: split package Chong Lu
2014-07-16 8:00 ` [PATCH 1/1] " Chong Lu
2014-07-16 13:04 ` Bruce Ashfield
2014-07-17 1:43 ` Chong Lu [this message]
2014-07-17 2:13 ` Bruce Ashfield
2014-07-17 6:58 ` Chong Lu
2014-07-17 7:04 ` Henning Heinold
2014-07-17 7:52 ` Chong Lu
2014-07-17 13:22 ` Bruce Ashfield
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=53C72A3A.50101@windriver.com \
--to=chong.lu@windriver.com \
--cc=bruce.ashfield@gmail.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