Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: RFC: magic libtool .la removal
Date: Tue, 18 Jun 2013 16:54:55 +0100	[thread overview]
Message-ID: <1371570895.6580.65.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <1371570476.20823.121.camel@ted>

On Tue, 2013-06-18 at 16:47 +0100, Richard Purdie wrote:
> We might as well throw away libtool

That sounds like an excellent plan to me.  I wonder how hard it would be
to invent a libtool-dummy script which took the same arguments but
basically just invoked the compiler and linker without any of the extra
craziness.

>Yes the .la files are annoying but they're not that much of a problem,
>are they?

I do recall that I was moved to write my original patch because the .la
files were causing me an actual problem rather than just being a
nuisance.  I can't remember the details offhand unfortunately, though I
guess I could try re-enabling them again locally and see what breaks.

Also, the patch that I posted in the first place did use a
DISTRO_FEATURE to control whether you get .la files or not (and the
default was still to have them) so you would be welcome to keep them on
for poky if you wanted.

p.




  parent reply	other threads:[~2013-06-18 15:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 14:31 RFC: magic libtool .la removal Burton, Ross
2013-06-18 14:42 ` Phil Blundell
2013-06-18 14:56   ` Burton, Ross
2013-06-18 15:00     ` Colin Walters
2013-06-18 15:05       ` Burton, Ross
2013-06-18 15:47         ` Richard Purdie
2013-06-18 15:52           ` Burton, Ross
2013-06-18 15:54           ` Phil Blundell [this message]
2013-06-18 15:59             ` Burton, Ross
2013-06-18 16:05           ` Colin Walters
2013-06-18 16:39             ` Colin Walters

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=1371570895.6580.65.camel@phil-desktop.brightsign \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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