From: Phil Blundell <pb@pbcl.net>
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 16:19:21 +0100 [thread overview]
Message-ID: <1309533561.2633.76.camel@phil-desktop> (raw)
In-Reply-To: <469c48cf5611c9e984d8114a48e834d03c44d099.1309533254.git.richard.purdie@linuxfoundation.org>
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.
p.
next prev parent reply other threads:[~2011-07-01 15:23 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 [this message]
2011-07-01 22:12 ` Richard Purdie
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=1309533561.2633.76.camel@phil-desktop \
--to=pb@pbcl.net \
--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