Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Colin Walters <walters@verbum.org>
Cc: Phil Blundell <philb@gnu.org>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] util-linux: Remove static libraries from -dev packages
Date: Wed, 26 Sep 2012 09:49:32 +0100	[thread overview]
Message-ID: <1348649372.8662.90.camel@ted> (raw)
In-Reply-To: <1348611089.2853.7.camel@lenny>

On Tue, 2012-09-25 at 18:11 -0400, Colin Walters wrote:
> On Tue, 2012-09-25 at 23:00 +0100, Phil Blundell wrote:
> 
> > That'd be inconsistent with other packages, since we do generally build
> > and ship the static libraries.  Having a big switch to turn off static
> > libraries globally seems like a fine plan, but I can't see any obvious
> > reason why the util-linux ones are any more useless than the rest.
> 
> Makes sense.  I wonder if there are actually any users of the static
> libraries.
> 
> For what it's worth in gnome-ostree I do just globally pass
> --disable-static by default.

I tested this a while back to see what performance difference it made.
The answer was "nothing too significant", I don't have the exact timings
handy. I do remember having to exclude sqlite-native from the list since
pseudo static links against it.

Cheers,

Richard




  reply	other threads:[~2012-09-26  9:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 12:54 [PATCH] util-linux: Remove static libraries from -dev packages Phil Blundell
2012-09-25 21:59 ` Colin Walters
2012-09-25 22:00   ` Phil Blundell
2012-09-25 22:11     ` Colin Walters
2012-09-26  8:49       ` Richard Purdie [this message]
2012-09-26  9:28         ` Phil Blundell
2012-09-26 14:05           ` Richard Purdie
2012-09-30 16:22             ` Phil Blundell
2012-09-26 14:50       ` Mark Hatle
2012-09-27 15:42 ` Saul Wold

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=1348649372.8662.90.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philb@gnu.org \
    --cc=walters@verbum.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