From: Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Config.in for both Qt4 and Qt5 in grantlee
Date: Sun, 09 Nov 2014 02:53:04 +0100 [thread overview]
Message-ID: <545EC900.9030103@gmail.com> (raw)
Dear All,
i'm trying to update the package grantlee (http://grantlee.org) in
Buildroot to the current upstream version. Historically grantlee
supported only Qt4 (this version is present now in Buildroot), and for a
while both Qt4 and Qt5, and with the last release it dropped the Qt4
support.
As for one of my legacy projects i still might need the Qt4 version, i
would like to keep the Qt4 support by using the last upstream version
which built on Qt4 when Buildroot configured to build Qt4, and use the
newest version when build on Qt5. It's easy to implement in the .mk file
with "ifeq ($(BR2_PACKAGE_QT),y)", although i'm not sure this is the
most elegant solution. (qjson using this for example to distinguish the
dependencies between the two Qt version, but it doesn't use 2 different
upstream versions for the 2 Qt versions)
I got into trouble in the Config.in though. Currently the grantlee.mk
selects a few Qt options with the kconfig 'select' statement (namely
BR2_PACKAGE_QT_STL, BR2_PACKAGE_QT_SCRIPT, BR2_PACKAGE_QT_GUI_MODULE),
and it also supposed to select the corresponding Qt5 options, but i
can't find any explicit trace that using conditional 'select' is
possible in kconfig, nor the correct syntax to express this.
What is the preferred solution to handle this scenario? Would it be
better to have a new grantlee package (let's say grantleeqt5) for this
latest version, and enable it in the menu only for Qt5? Or is there any
kconfig trick i could use here? An other option would be just to drop
Qt4 support (if the upstream already did it) at least in the official
Buildroot version (and i can use any nasty trick in my own Buildroot
tree to support my legacy project till i'm able to port it to Qt5). Is
there anybody out there who is using this lib with Qt4?
Thanks in advance, regards
zgyarmati
next reply other threads:[~2014-11-09 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 1:53 Zoltan Gyarmati [this message]
2014-11-09 19:12 ` [Buildroot] Config.in for both Qt4 and Qt5 in grantlee Thomas Petazzoni
2014-11-09 23:43 ` Zoltan Gyarmati
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=545EC900.9030103@gmail.com \
--to=mr.zoltan.gyarmati@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox