From: Philip Balister <philip@balister.org>
To: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
Cc: openembedded-core@openembedded.org
Subject: Re: [PATCH] distutils-common : Add -staticdev to PACKAGES.
Date: Wed, 21 Nov 2012 07:59:55 -0500 [thread overview]
Message-ID: <50ACD04B.4020009@balister.org> (raw)
In-Reply-To: <50AC6EA2.60708@herbrechtsmeier.net>
On 11/21/2012 01:03 AM, Stefan Herbrechtsmeier wrote:
> Am 20.11.2012 23:58, schrieb Philip Balister:
>> Some python recipes may build static libraries that need packaging in
>> {PN}-static-dev.
>>
>> This change fixes a QA error in python-numpy.
>>
>> Signed-off-by: Philip Balister <philip@balister.org>
>> ---
>> meta/classes/distutils-common-base.bbclass | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/classes/distutils-common-base.bbclass
>> b/meta/classes/distutils-common-base.bbclass
>> index f66a5cd..36c1e83 100644
>> --- a/meta/classes/distutils-common-base.bbclass
>> +++ b/meta/classes/distutils-common-base.bbclass
>> @@ -5,7 +5,7 @@ EXTRA_OEMAKE = ""
>> export STAGING_INCDIR
>> export STAGING_LIBDIR
>> -PACKAGES = "${PN}-dev ${PN}-dbg ${PN}-doc ${PN}"
>> +PACKAGES = "${PN}-staticdev ${PN}-dev ${PN}-dbg ${PN}-doc ${PN}"
>> FILES_${PN} = "${bindir}/* ${libdir}/* ${libdir}/${PYTHON_DIR}/*"
> Hi,
>
> I post a similarly patch parallel with the python-numpy fix:
> http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/29575
Provided the:
+FILES_${PN}-staticdev += "\
+ ${PYTHON_SITEPACKAGES_DIR}/*.a \
+"
Actually catches a lot of the .a files, I prefer Stefan's version. Numpy
still needs to to override the FILES though.
Philip
PS: WARNING, I am not a python expert, just trying to help fix QA issues
as they come up.
>
> Regards,
> Stefan
>
prev parent reply other threads:[~2012-11-21 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 22:58 [PATCH] distutils-common : Add -staticdev to PACKAGES Philip Balister
2012-11-21 6:03 ` Stefan Herbrechtsmeier
2012-11-21 12:59 ` Philip Balister [this message]
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=50ACD04B.4020009@balister.org \
--to=philip@balister.org \
--cc=openembedded-core@openembedded.org \
--cc=stefan@herbrechtsmeier.net \
/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