From: Daniel Mack <zonque@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Qt: add config option to build libQtDeclarative module
Date: Tue, 31 May 2011 18:16:34 +0200 [thread overview]
Message-ID: <1306858594-28995-1-git-send-email-zonque@gmail.com> (raw)
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
package/qt/Config.in | 7 +++++++
package/qt/qt.mk | 9 +++++++++
2 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/package/qt/Config.in b/package/qt/Config.in
index 4a3945c..214f140 100644
--- a/package/qt/Config.in
+++ b/package/qt/Config.in
@@ -378,4 +378,11 @@ config BR2_PACKAGE_QT_SCRIPTTOOLS
Build the Qt Script Tools module.
if unsure, say n.
+config BR2_PACKAGE_QT_DECLARATIVE
+ bool "Declarative module"
+ depends on BR2_PACKAGE_QT_GUI_MODULE
+ help
+ Build the Qt Declarative Module for qml support
+ if unsure, say n.
+
endif # BR2_PACKAGE_QT
diff --git a/package/qt/qt.mk b/package/qt/qt.mk
index 8bcbd3f..e8b7a49 100644
--- a/package/qt/qt.mk
+++ b/package/qt/qt.mk
@@ -398,6 +398,12 @@ else
QT_CONFIGURE_OPTS += -no-stl
endif
+ifeq ($(BR2_PACKAGE_QT_DECLARATIVE),y)
+QT_CONFIGURE_OPTS += -declarative
+else
+QT_CONFIGURE_OPTS += -no-declarative
+endif
+
# ccache and precompiled headers don't play well together
ifeq ($(BR2_CCACHE),y)
QT_CONFIGURE_OPTS += -no-pch
@@ -535,6 +541,9 @@ endif
ifeq ($(BR2_PACKAGE_QT_SCRIPTTOOLS),y)
QT_INSTALL_LIBS += QtScriptTools
endif
+ifeq ($(BR2_PACKAGE_QT_DECLARATIVE),y)
+QT_INSTALL_LIBS += QtDeclarative
+endif
ifeq ($(BR2_PACKAGE_QT_QT3SUPPORT),y)
QT_INSTALL_LIBS += Qt3Support
endif
--
1.7.5.1
next reply other threads:[~2011-05-31 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 16:16 Daniel Mack [this message]
2011-06-07 8:36 ` [Buildroot] [PATCH] Qt: add config option to build libQtDeclarative module Daniel Mack
2011-06-17 9:07 ` Daniel Mack
2011-06-17 11:30 ` Daniel Nyström
2011-06-20 10:06 ` Peter Korsgaard
2011-06-20 11:33 ` Daniel Mack
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=1306858594-28995-1-git-send-email-zonque@gmail.com \
--to=zonque@gmail.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.