From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 5/6] beecrypt: Fix up packaging QA warnings
Date: Fri, 01 Jul 2011 23:12:38 +0100 [thread overview]
Message-ID: <1309558358.20015.563.camel@rex> (raw)
In-Reply-To: <1309533561.2633.76.camel@phil-desktop>
On Fri, 2011-07-01 at 16:19 +0100, Phil Blundell wrote:
> On Fri, 2011-07-01 at 16:17 +0100, Richard Purdie wrote:
> > +FILES_${PN} = "${sysconfdir} ${libdir}/*.so.* ${libdir}/${BPN}/*.so.*"
>
> You can use ${SOLIBS} there...
>
> > +FILES_${PN}-dev += "${libdir}/${BPN}/*.so ${libdir}/${BPN}/*.la
>
> ... and ${SOLIBSDEV} there.
I'm in two minds on these. On the one hand they do make sense and have
allowed us to build darwin targets in the past (and would extend to
windows too). On the other hand nobody is using them outside the core
metadata.
I think a global search and replace would likely be the best move if we
decide they're a good thing...
Cheers,
Richard
next prev parent reply other threads:[~2011-07-01 22:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 15:17 [PATCH 0/6] QA Warnings Cleanup Richard Purdie
2011-07-01 15:17 ` [PATCH 1/6] cairo: Clean up packaging and fix warnings Richard Purdie
2011-07-01 15:17 ` [PATCH 2/6] kernel.bbclass: Ensure kernel/* internal sysroot working directory don't get packaged Richard Purdie
2011-07-01 15:17 ` [PATCH 3/6] libpcre: Fix QA warnings Richard Purdie
2011-07-01 15:17 ` [PATCH 4/6] python: Ensure libpython.so ends up in the .dev package Richard Purdie
2011-07-01 15:17 ` [PATCH 5/6] beecrypt: Fix up packaging QA warnings Richard Purdie
2011-07-01 15:19 ` Phil Blundell
2011-07-01 22:12 ` Richard Purdie [this message]
2011-07-02 7:40 ` Koen Kooi
2011-07-05 10:20 ` Phil Blundell
2011-07-01 15:17 ` [PATCH 6/6] insane.bbclass: Start to rework this so specific checks can be easily made warnings/errors Richard Purdie
2011-07-01 22:29 ` [PATCH 0/6] QA Warnings Cleanup Richard Purdie
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=1309558358.20015.563.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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