All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] qwt: compile as a static lib if QT_SHARED is not selected
Date: Mon, 26 Jan 2015 12:21:41 +0100	[thread overview]
Message-ID: <20150126122141.437dd519@free-electrons.com> (raw)
In-Reply-To: <54C60A2A.9090805@gmail.com>

Dear Richard Genoud,

On Mon, 26 Jan 2015 10:34:34 +0100, Richard Genoud wrote:

> > I agree that it would be cleaner, but the reason the explicit QT_SHARED
> > stuff was added was afaik a lot of systems only needed Qt in a single
> > application / that application only used a subset of the Qt
> > functionality, so having a static libQt while everything else was shared
> > was quite a big win in size / startup time.
> 
> yes, that's exactly my case. I've got one single Qt application, and Qt
> is quite huge, so making it static saves a lot of space.
> I didn't trying to compile with BR2_STATIC_LIBS=y, but I guess that my
> rootfs will be much bigger.

Probably. Unfortunately with kconfig, we cannot easily add one option
for debug symbols, static/dynamic linking to each package. It would add
gazillions of options.

One possibility would be to have one global string option that you
could fill in with a space-separated list of packages that you want to
be built statically, even if the rest of the system is built
dynamically.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2015-01-26 11:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 10:17 [Buildroot] [PATCH 1/2] qwt: compile as a static lib if QT_SHARED is not selected Richard Genoud
2015-01-20 10:17 ` [Buildroot] [PATCH 2/2] qwt: add license information Richard Genoud
2015-01-20 16:47   ` Thomas Petazzoni
2015-01-20 16:45 ` [Buildroot] [PATCH 1/2] qwt: compile as a static lib if QT_SHARED is not selected Thomas Petazzoni
2015-01-23 16:00   ` Richard Genoud
2015-01-23 16:06     ` Yann E. MORIN
2015-01-23 16:19       ` Richard Genoud
2015-01-25 22:20   ` Peter Korsgaard
2015-01-26  9:34     ` Richard Genoud
2015-01-26  9:54       ` Peter Korsgaard
2015-01-26 10:16         ` Richard Genoud
2015-01-26 11:21       ` Thomas Petazzoni [this message]
2015-01-26 17:00         ` Richard Genoud
2015-01-26 17:11           ` Thomas Petazzoni
2015-01-27 20:42     ` Arnout Vandecappelle
2015-01-27 20:55       ` Peter Korsgaard
2015-01-28  9:35         ` Richard Genoud

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=20150126122141.437dd519@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.