From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 02/17] connman: Package unpackaged .la file
Date: Wed, 06 Jul 2011 10:14:05 +0100 [thread overview]
Message-ID: <1309943646.6337.5.camel@phil-desktop> (raw)
In-Reply-To: <d0bae3ed1b9aead05a353ade871e71bf5b1c01b1.1309906154.git.richard.purdie@linuxfoundation.org>
On Tue, 2011-07-05 at 23:51 +0100, Richard Purdie wrote:
> +FILES_${PN}-dev += "${libdir}/connman/plugins/*.la"
Actually, in this specific case, I think adding *.la to FILES is the
wrong thing to do. The DSOs in question are plugins, not libraries, and
nobody is ever going to link against them. So the corresponding .la
files (and the .so symlinks, if those are also getting created) really
are just dross and should be deleted.
p.
next prev parent reply other threads:[~2011-07-06 9:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 22:51 [PATCH 00/17] Various QA/unpackaged files cleanups Richard Purdie
2011-07-05 22:51 ` [PATCH 01/17] gcc: Fix unpackaged files warnings, broken symlink and superfluous files Richard Purdie
2011-07-05 22:51 ` [PATCH 02/17] connman: Package unpackaged .la file Richard Purdie
2011-07-06 9:14 ` Phil Blundell [this message]
2011-07-06 10:34 ` Richard Purdie
2011-07-05 22:51 ` [PATCH 03/17] tslib: " Richard Purdie
2011-07-05 22:51 ` [PATCH 04/17] btrfs-tools: Fix manpage creation directory Richard Purdie
2011-07-05 22:51 ` [PATCH 05/17] xcb-proto: Package unshipped files, create python-xcbgen package for python xcbgen code Richard Purdie
2011-07-05 22:51 ` [PATCH 06/17] eds-dbus: Package unpackaged files Richard Purdie
2011-07-05 22:51 ` [PATCH 07/17] systemtap: Don't set prefix to a path including so examples get placed in the correct path and packaged correctly Richard Purdie
2011-07-05 22:51 ` [PATCH 08/17] qt4: Package debug source files Richard Purdie
2011-07-05 22:51 ` [PATCH 09/17] telepathy-python: Remove unneeded and unpackaged files Richard Purdie
2011-07-05 22:51 ` [PATCH 10/17] librsvg: Clean up " Richard Purdie
2011-07-05 22:51 ` [PATCH 11/17] gtk-engines: Package " Richard Purdie
2011-07-05 22:51 ` [PATCH 12/17] x11perf: Packaged " Richard Purdie
2011-07-05 22:51 ` [PATCH 13/17] apt: Package " Richard Purdie
2011-07-06 9:17 ` Phil Blundell
2011-07-06 10:25 ` Richard Purdie
2011-07-05 22:51 ` [PATCH 14/17] git: Package up python and gitweb files into appropriate packages Richard Purdie
2011-07-05 22:51 ` [PATCH 15/17] kernelshark/trace-cmd: Clean up QA warnings including fising LDFLAGS issues Richard Purdie
2011-07-06 9:15 ` Phil Blundell
2011-07-05 22:51 ` [PATCH 16/17] opensp: Add unpackaged files Richard Purdie
2011-07-05 22:51 ` [PATCH 17/17] chrpath: Ensure the package respects the docdir variable Richard Purdie
2011-07-06 2:59 ` [PATCH 00/17] Various QA/unpackaged files cleanups Otavio Salvador
2011-07-06 8:03 ` Richard Purdie
2011-07-06 9:06 ` Phil Blundell
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=1309943646.6337.5.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