From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] qt5: expose a QT5_QMAKE variable for other Qt5 packages
Date: Mon, 3 Nov 2014 22:46:20 +0100 [thread overview]
Message-ID: <20141103224620.5c3ffe1d@free-electrons.com> (raw)
In-Reply-To: <87fve02cbm.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Mon, 03 Nov 2014 22:39:41 +0100, Peter Korsgaard wrote:
> >> Should we just use BR2_PACKAGE_QT5BASE everywhere you check for BR2_PACKAGE_QT5?
>
> > Where exactly? Or shouldn't we have qt5base selected as soon as qt5 is
> > enabled?
>
> Well, that's perhaps the easiest solution, yes. Having qt5 enabled but
> not qt5base doesn't make any sense.
>
> Will you send an updated series or should I do that here?
I can, but not this week. I'm busy giving a training, and will not have
much free time.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-03 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 22:15 [Buildroot] [PATCH 1/4] package: prepare to support modules that work with Qt or Qt5 Thomas Petazzoni
2014-11-01 22:15 ` [Buildroot] [PATCH 2/4] qt5: expose a QT5_QMAKE variable for other Qt5 packages Thomas Petazzoni
2014-11-02 22:46 ` Peter Korsgaard
2014-11-03 21:25 ` Thomas Petazzoni
2014-11-03 21:39 ` Peter Korsgaard
2014-11-03 21:46 ` Thomas Petazzoni [this message]
2014-11-03 22:00 ` Peter Korsgaard
2014-11-01 22:15 ` [Buildroot] [PATCH 3/4] qjson: allow building with Qt5 Thomas Petazzoni
2014-11-01 22:15 ` [Buildroot] [PATCH 4/4] qextserialport: " Thomas Petazzoni
2014-11-03 22:07 ` [Buildroot] [PATCH 1/4] package: prepare to support modules that work with Qt or Qt5 Peter Korsgaard
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=20141103224620.5c3ffe1d@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.