From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qtuio: depends on QT4
Date: Thu, 04 Apr 2013 13:52:11 +0200 [thread overview]
Message-ID: <515D696B.9080608@mind.be> (raw)
In-Reply-To: <1364662519-2385-1-git-send-email-sho@relinux.de>
On 30/03/13 17:55, Stephan Hoffmann wrote:
> Fixes: http://autobuild.buildroot.net/results/e6501a7a487ec3a02463ad0f3aa60168883fa369/
>
> Signed-off-by: Stephan Hoffmann <sho@relinux.de>
> ---
> package/qtuio/Config.in | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/package/qtuio/Config.in b/package/qtuio/Config.in
> index 19499fd..590b2de 100644
> --- a/package/qtuio/Config.in
> +++ b/package/qtuio/Config.in
> @@ -1,6 +1,6 @@
> config BR2_PACKAGE_QTUIO
> bool "qtuio"
> - depends on BR2_PACKAGE_QT_GUI_MODULE
> + depends on BR2_PACKAGE_QT_GUI_MODULE && !BR2_PACKAGE_QT5
Thomas has a patch pending which makes qt4 and qt5 mutually exclusive
(because any qt package will fail if both are installed, because of
inconsistencies in the qmake configurations). So this change should be
redundant.
> help
> Implementation of an interface connecting TUIO messages
> and QT events
> @@ -16,3 +16,5 @@ config BR2_QTUIO_EXAMPLES
> comment "qtuio depends on QT gui module"
> depends on !BR2_PACKAGE_QT_GUI_MODULE
>
> +comment "qtuio requires QT4"
> + depends on BR2_PACKAGE_QT5
This one may still be useful though.
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
prev parent reply other threads:[~2013-04-04 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 16:55 [Buildroot] [PATCH] qtuio: depends on QT4 Stephan Hoffmann
2013-04-04 11:52 ` Arnout Vandecappelle [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=515D696B.9080608@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox