From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gustavo Zacarias Date: Mon, 26 May 2014 08:03:48 -0300 Subject: [Buildroot] [WIP PATCH 2/5] gcc-final: disable shared build for static In-Reply-To: <20140526122419.213075c3@free-electrons.com> References: <1401055980-28742-1-git-send-email-gustavo@zacarias.com.ar> <1401055980-28742-3-git-send-email-gustavo@zacarias.com.ar> <20140526113840.3473ed77@free-electrons.com> <53831210.40406@zacarias.com.ar> <20140526122419.213075c3@free-electrons.com> Message-ID: <53831F94.7000900@zacarias.com.ar> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On 05/26/2014 07:24 AM, Thomas Petazzoni wrote: > There is an advantage with the pure dynamic scenario: build time. > > When you have dyn+static, you build all object files (for packages that > do it correctly): once for static without -fPIC, and once for dynamic > with -fPIC. Here is what I have in my commit log about this: > > 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. Regards.