Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] qt5base: unconditionally install Qt5printSupport if widgets are enabled
Date: Thu, 13 Nov 2014 16:33:08 +0100	[thread overview]
Message-ID: <87ioiji097.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20141113162635.673fe030@free-electrons.com> (Thomas Petazzoni's message of "Thu, 13 Nov 2014 16:26:35 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > Dear Peter Korsgaard,
 > On Thu, 13 Nov 2014 16:17:08 +0100, Peter Korsgaard wrote:

 >> > So why have a Config.in option for this in the first place?
 >> 
 >> Just because I wanted to make as minimal as possible a change now that
 >> we're past -rc1.

 > That makes sense.

Good ;)

 >> I don't follow qt5 development, but presumably this
 >> used to be user settable and could become so again in future qt5
 >> releases.

 > That however seems like a pretty weak argument :-) Do we keep or add
 > options just because they may hypothetically be useful in the future?

I agree it is a bit weak ;) I basically don't really know much about
qt5, so I wanted as minimal as possible a change.

I just noticed that we have the same issue with the network, sql, xml
and test modules, so I will make a similar change for those as well.

I find it quite a pity that qt5base apparently isn't very configurable
after all :/

-- 
Bye, Peter Korsgaard 

      reply	other threads:[~2014-11-13 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 14:48 [Buildroot] [git commit] qt5base: unconditionally install Qt5printSupport if widgets are enabled Peter Korsgaard
2014-11-13 15:03 ` Thomas Petazzoni
2014-11-13 15:17   ` Peter Korsgaard
2014-11-13 15:26     ` Thomas Petazzoni
2014-11-13 15:33       ` Peter Korsgaard [this message]

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=87ioiji097.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