From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Performance datapoint - impact of static libs
Date: Wed, 20 Jul 2011 15:50:54 +0100 [thread overview]
Message-ID: <1311173454.2344.53.camel@rex> (raw)
In-Reply-To: <1310737071.3805.38.camel@phil-desktop>
On Fri, 2011-07-15 at 14:37 +0100, Phil Blundell wrote:
> > So static libs add an extra ~30mins of processing (7%) and ~5 mins to
> > the overall build time. Not as much of a gain as I'd have liked but
> > interesting none the less.
>
> Do you know how many packages actually respect the --disable-static
> flag? I don't think (e)glibc does, for example, which is a bit of a
> shame since it obviously has one of the largest build times.
I did a quick search over the resulting build looking for image/*.a
files and it seems a lot of the system did respect it. There were some
significant exceptions (eglibc, boost, openssl spring to mind) but in
general it looked pretty good.
Cheers,
Richard
prev parent reply other threads:[~2011-07-20 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 13:31 Performance datapoint - impact of static libs Richard Purdie
2011-07-15 13:37 ` Phil Blundell
2011-07-20 14:50 ` Richard Purdie [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=1311173454.2344.53.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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