From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [WIP PATCH 2/5] gcc-final: disable shared build for static
Date: Mon, 26 May 2014 14:05:27 +0200 [thread overview]
Message-ID: <20140526140527.3d6bd86c@free-electrons.com> (raw)
In-Reply-To: <53831F94.7000900@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 26 May 2014 08:03:48 -0300, Gustavo Zacarias wrote:
> > For example, a static+shared build of libglib2 takes 1 minutes
> > and 59 seconds, with a final build directory of 96 MB. A shared-only
> > build of libglib2 takes only 1 minutes and 31 seconds (almost a
> > 25% reduction of the build time), and the final build directory
> > weights 89 MB (a reduction of almost 8%).
> >
> > A 25% reduction in build time is certainly nice for users who don't
> > care about static libraries, no?
>
> Ok, so then we can go for it, i don't think anyone will care about the
> space saving though, but time is a whole different matter.
Agreed, the disk space saving nobody really cares, especially if it's
only ~8%. But a build time saving of 25% is quite nice, in my opinion.
Normally, all packages using libtool should be affected, but I haven't
checked.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-26 12:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 22:12 [Buildroot] [WIP PATCH 0/5] Static linking fixes Gustavo Zacarias
2014-05-25 22:12 ` [Buildroot] [WIP PATCH 1/5] uclibc: don't install tools to staging when static Gustavo Zacarias
2014-05-26 9:35 ` Thomas Petazzoni
2014-07-15 18:54 ` Thomas Petazzoni
2014-05-25 22:12 ` [Buildroot] [WIP PATCH 2/5] gcc-final: disable shared build for static Gustavo Zacarias
2014-05-26 9:37 ` Thomas Petazzoni
2014-05-26 10:04 ` Gustavo Zacarias
2014-05-26 10:07 ` Thomas Petazzoni
2014-05-26 11:02 ` Gustavo Zacarias
2014-05-26 9:38 ` Thomas Petazzoni
2014-05-26 10:06 ` Gustavo Zacarias
2014-05-26 10:24 ` Thomas Petazzoni
2014-05-26 11:03 ` Gustavo Zacarias
2014-05-26 12:05 ` Thomas Petazzoni [this message]
2014-05-25 22:12 ` [Buildroot] [WIP PATCH 3/5] libiconv: disable preloadable for static builds Gustavo Zacarias
2014-05-25 22:12 ` [Buildroot] [WIP PATCH 4/5] package infra: revert 0a4bd19f Gustavo Zacarias
2014-05-25 22:13 ` [Buildroot] [WIP PATCH 5/5] package infra: add -static to C/CXXFLAGS Gustavo Zacarias
2014-05-26 8:13 ` [Buildroot] [WIP PATCH 0/5] Static linking fixes Thomas De Schampheleire
2014-05-26 10:02 ` Gustavo Zacarias
2014-07-30 21:42 ` Thomas Petazzoni
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=20140526140527.3d6bd86c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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