From: Trevor Woerner <trevor.woerner@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Qt in OE-core
Date: Tue, 07 Jan 2014 13:27:22 -0500 [thread overview]
Message-ID: <52CC470A.9030302@linaro.org> (raw)
Hello everyone,
question:
Should some version of Qt be included in openembedded-core, or should
all recipes to add Qt be part of their own version-specific Qt layer?
background:
openembedded-core[1] used to include recipes for Qt3, but as Qt3 became
old these recipes were replaced with Qt4 and the Qt3 support was broken
out into its own layer[2]. We're now at a point where Qt4 is getting old
and Qt5 is "current". At some point we'll have to replace the Qt4
support in [1] with support for Qt5. But we expect users will still want
to use Qt4, so if the Qt4 support in [1] is replaced by support for Qt5,
the Qt4 support will need to be broken out into its own layer. Qt5
support is currently being developed on it's own layer[3].
This email thread is *not* to discuss when we should replace Qt4 with
Qt5, then question is: should [1] include *any* Qt support, or should Qt
be always in its own layer to be added as required by the distribution?
If we decide [1] should provide some Qt support, then we can discuss
when we should replace the Qt4 support with Qt5 in [1]. But for now it
would be nice to reach a consensus on whether or not [1] should include
any Qt support at all or if it wouldn't just be easier to always have Qt
support in its own version-specific layers to be added as required (if
needed) by the distribution configuration.
Thanks for your feedback.
[1]
http://layers.openembedded.org/layerindex/branch/master/layer/openembedded-core/
[2] http://layers.openembedded.org/layerindex/branch/master/layer/meta-qt3/
[3] http://layers.openembedded.org/layerindex/branch/master/layer/meta-qt5/
next reply other threads:[~2014-01-07 18:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 18:27 Trevor Woerner [this message]
2014-01-07 19:23 ` Qt in OE-core Martin Jansa
2014-01-08 10:28 ` Richard Purdie
2014-01-09 14:21 ` Trevor Woerner
2014-01-08 12:05 ` Otavio Salvador
2014-01-08 15:56 ` Paul Eggleton
2014-01-08 16:29 ` Martin Jansa
2014-01-08 18:44 ` Trevor Woerner
2014-01-08 19:39 ` Martin Jansa
2014-01-08 23:21 ` Paul Eggleton
2014-01-08 23:57 ` Richard Purdie
2014-01-09 0:06 ` Philip Balister
2014-01-09 0:32 ` Martin Jansa
2014-01-09 6:32 ` Koen Kooi
2014-01-09 12:57 ` Otavio Salvador
2014-01-09 12:56 ` Otavio Salvador
2014-01-09 15:17 ` Phil Blundell
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=52CC470A.9030302@linaro.org \
--to=trevor.woerner@linaro.org \
--cc=openembedded-core@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