public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: Please review: function epunt_la_files for eutils.eclass
Date: Sat, 15 Nov 2008 02:26:52 +0200	[thread overview]
Message-ID: <1226708812.12338.3.camel@localhost> (raw)
In-Reply-To: <200811150005.54423.loki_val@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]

On Sat, 2008-11-15 at 00:05 +0100, Peter Alfredsen wrote:
> Anyway, we really need to start punting .la files one way or the other. 
> For desktop users of our distro, they do a lot more harm than good. For 
> embedded, perhaps static linking serves some purpose, but really, if 
> you can't afford dynamic linking, what are you going to run on your 
> board?

Just to quickly explain the purpose of static linking on embedded - it
has nothing to do with avoiding dynamic linking (run-time?) cost, it has
everything to do with size. If you have a library that only one or few
applications use, you can end up with smaller size through static
linking it, rather than using a shared library of it.
This is because during static linking all functions that are not used
can be discarded from the final binary, while with shared libraries all
the code has to remain, because it isn't know what will be using that
shared library, so the toolchain can not safely discard anything, even
if you just have one application using some big library, but only using
a small subset of its functionality.


-- 
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-11-15  0:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-09 16:04 [gentoo-dev] Please review: function epunt_la_files for eutils.eclass Peter Alfredsen
2008-11-09 16:10 ` Fabian Groffen
2008-11-09 16:34   ` Peter Alfredsen
2008-11-09 16:48     ` Fabian Groffen
2008-11-09 17:46       ` Peter Alfredsen
2008-11-09 17:53         ` Fabian Groffen
2008-11-12 13:41     ` Mart Raudsepp
2008-11-12 14:40       ` Peter Alfredsen
2008-11-12 16:14         ` Rémi Cardona
2008-11-12 17:16           ` Peter Alfredsen
2008-11-13  6:21             ` Donnie Berkholz
2008-11-14 10:35             ` Gilles Dartiguelongue
2008-11-14 17:28               ` Marius Mauch
2008-11-14 14:25             ` Alexis Ballier
2008-11-14 14:35               ` Rémi Cardona
2008-11-16  8:44                 ` Michael Haubenwallner
2008-11-16 22:21                   ` Rémi Cardona
2008-11-14 22:31               ` Donnie Berkholz
2008-11-14 22:33                 ` Ciaran McCreesh
2008-11-14 22:44               ` David Leverton
2008-11-12 16:53         ` Mart Raudsepp
2008-11-12 17:31           ` Peter Alfredsen
2008-11-13 18:49             ` [gentoo-dev] " Ryan Hill
2008-11-14  4:14             ` Ryan Hill
2008-11-14 23:05               ` Peter Alfredsen
2008-11-14 23:25                 ` Ciaran McCreesh
2008-11-15  0:26                 ` Mart Raudsepp [this message]
2008-11-15  6:44                   ` Duncan
2008-11-17 19:19                 ` [gentoo-dev] " Steve Long
2008-11-12 15:52     ` [gentoo-dev] " Donnie Berkholz
2008-11-12 16:24       ` Peter Alfredsen
2008-11-13  6:23         ` Donnie Berkholz

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=1226708812.12338.3.camel@localhost \
    --to=leio@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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