From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] qwt: compile as a static lib if QT_SHARED is not selected
Date: Sun, 25 Jan 2015 23:20:55 +0100 [thread overview]
Message-ID: <87siey4i48.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20150120174507.1d11ab61@free-electrons.com> (Thomas Petazzoni's message of "Tue, 20 Jan 2015 17:45:07 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Dear Richard Genoud,
> On Tue, 20 Jan 2015 11:17:28 +0100, Richard Genoud wrote:
>> If Qt is compile as a static library, there's no point compiling qwt as
>> a shared library, otherwise, we will have a huge qwt lib and a huge Qt
>> application.
>>
>> Signed-off-by: Richard Genoud <richard.genoud@gmail.com>
>>
>> +ifeq ($(BR2_PACKAGE_QT_SHARED),y)
>> + QWT_CONFIG += -e 's/^.*QWT_CONFIG.*QwtDll.*$$/QWT_CONFIG += QwtDll/'
>> +else
>> + QWT_CONFIG += -e 's/^.*QWT_CONFIG.*QwtDll.*$$/\# QWT_CONFIG += QwtDll/'
>> +endif
> I think we should get rid of BR2_PACKAGE_QT_SHARED completely, and use
> BR2_STATIC_LIBS here instead.
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.
It does complicate LGPL compliance and I don't know if the disk space
concerns are as big these days though.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-01-25 22:20 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 [this message]
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
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=87siey4i48.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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