All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] qextserialport: don't require Qt GUI module
Date: Thu, 07 Feb 2013 08:00:07 +0100	[thread overview]
Message-ID: <511350F7.9060504@mind.be> (raw)
In-Reply-To: <50A580BA.5020402@mind.be>

On 16/11/12 00:54, Arnout Vandecappelle wrote:
[snip]
>> +diff -Nrup qextserialport-f83b4e7ca922e53.orig/qextserialport.pro
>> qextserialport-f83b4e7ca922e53/qextserialport.pro
>> +--- qextserialport-f83b4e7ca922e53.orig/qextserialport.pro 2012-10-17 09:13:53.000000000 +0200
>> ++++ qextserialport-f83b4e7ca922e53/qextserialport.pro    2012-11-13 22:48:29.249431510 +0100
>> +@@ -41,6 +41,8 @@ macx:qesp_mac_framework {
>> +
>> + win32|mac:!wince*:!win32-msvc:!macx-xcode:CONFIG += debug_and_release
>> build_all
>> +
>> ++!win32*:!wince*:QT -= gui
>> ++
>> + #generate proper library name
>> + greaterThan(QT_MAJOR_VERSION, 4) {
>> +     QESP_LIB_BASENAME = QtExtSerialPort
>
>   After submitting this patch upstream, the feedback I got is that it should
> not be necessary to do this.  Looking a bit deeper, it turns out they are
> right, in a way.  We use the qws mkspecs file, which includes
> QT += core gui network
>
>   I.e., by default the gui will always be linked in, and -DQT_GUI_LIB  will be added
> to the compile flags. It seems logical that Qt would remove the ones that aren't
> installed, but it doesn't.  So we should do it ourselves.
>
>   While we're at it, we could also throw out our patching of the platform-specific
> qws config file: we are anyway replacing all "interesting" variables with our own
> values, so all useful content is thrown away.  Instead, we could make our own spec
> file that contains exactly what we need:
>
> include(../../common/linux.conf)
> include(../../common/gcc-base-unix.conf)
> include(../../common/g++-unix.conf)
> include(../../common/qws.conf)
> <our stuff goes here>
> load(qt_config)
>
>
>   What do you think?


  Thomas,

  Now that you're working on Qt5, maybe you can check with qt-project if 
this is indeed the way to go?

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2013-02-07  7:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 21:44 [Buildroot] [git commit] qextserialport: don't require Qt GUI module Peter Korsgaard
2012-11-15 23:54 ` Arnout Vandecappelle
2012-11-16  6:26   ` Peter Korsgaard
2012-11-16  7:44     ` Thomas Petazzoni
2013-02-07  7:00   ` Arnout Vandecappelle [this message]
2013-02-07  8:24     ` 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=511350F7.9060504@mind.be \
    --to=arnout@mind.be \
    --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.