From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH] navit: enable qml build
Date: Thu, 10 Jun 2010 22:07:37 +0200 [thread overview]
Message-ID: <1276200457-11650-1-git-send-email-Martin.Jansa@gmail.com> (raw)
* but for now without DEPENDS on qt4-x11-free, because 4.7.0 is not yet
released and building qt4-x11-free just because of navit (for someone
not using it for something else) takes a lot of time
* should I add qt as DISTRO_FEATURE like "tk" is used in python DEPENDS?
* I'll add PR bump before pushing, if it's OK to enable it without
forced qt4 depends (navit build before qt-4.7 wont have qml and
rebuilded navit after building qt-4.7 will get qml support)
* At least it doesn't fail without qt, even when it's enabled in
configure param
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
recipes/navit/navit_svn.bb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/recipes/navit/navit_svn.bb b/recipes/navit/navit_svn.bb
index 2b75c4e..61d5e24 100644
--- a/recipes/navit/navit_svn.bb
+++ b/recipes/navit/navit_svn.bb
@@ -15,7 +15,7 @@ RDEPENDS_${PN} = " navit-icons ${PN}-config "
DEPENDS_append_shr = " gypsy"
RDEPENDS_append_shr = " fsoraw"
-EXTRA_OECONF += " --enable-svg2png-scaling-flag=32 --disable-speech-speech-dispatcher --enable-cache-size=20971520"
+EXTRA_OECONF += " --enable-svg2png-scaling-flag=32 --disable-speech-speech-dispatcher --enable-cache-size=20971520 --enable-gui-qml"
SRC_URI = "svn://anonymous@navit.svn.sourceforge.net/svnroot/navit/trunk;module=navit;proto=https"
--
1.7.1
next reply other threads:[~2010-06-10 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 20:07 Martin Jansa [this message]
2010-06-11 5:53 ` [PATCH] navit: enable qml build Holger Freyther
2010-06-11 6:18 ` Martin Jansa
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=1276200457-11650-1-git-send-email-Martin.Jansa@gmail.com \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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