From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] .la files cleanup
Date: Mon, 03 Oct 2011 13:28:42 -0700 [thread overview]
Message-ID: <4E8A1AFA.3060409@gmail.com> (raw)
In-Reply-To: <1317653702.13337.4.camel@phil-desktop>
On 10/3/2011 7:55 AM, Phil Blundell wrote:
> On Mon, 2011-10-03 at 14:58 +0400, Dmitry Eremin-Solenikov wrote:
>> My proposal would be to include a special task or a
>> do_install_append() part that
>> will remove specified .la files. (like ${libdir}/xorg/modules/*/.la,
>> ${libdir}/matchbox-panel/*.la, etc.). I see this usually done in
>> do_install or in special do_install_append
>> parts, but I think it would be better to handle this globally.
>
> I guess the ideal solution would be to find a way to stop libtool from
> installing these things in the first place. It isn't totally obvious to
> me that the .la files are a net benefit even for real shared libraries,
> and for plugins I think they are probably a net loss in most/all cases.
>
I also have this opinion. I think we need to experiment by not
installing .la at all and see what breaks. I would guess very little
> When this issue last came up it seemed that Richard's preferred fix was
> to just ship the .la files in FILES_${PN}-dev, and I guess that approach
> does at least have the merit of simplicity. See:
>
> http://lists.linuxtogo.org/pipermail/openembedded-core/2011-July/005533.html
>
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2011-10-03 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 10:58 [RFC] .la files cleanup Dmitry Eremin-Solenikov
2011-10-03 11:32 ` Richard Purdie
2011-10-03 14:55 ` Phil Blundell
2011-10-03 17:06 ` Dmitry Eremin-Solenikov
2011-10-03 18:34 ` Otavio Salvador
2011-10-03 20:28 ` Khem Raj [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=4E8A1AFA.3060409@gmail.com \
--to=raj.khem@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