From: Philip Balister <philip@balister.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Future of Qt4 recipes
Date: Mon, 22 Jun 2015 18:50:50 -0400 [thread overview]
Message-ID: <5588914A.6020705@balister.org> (raw)
In-Reply-To: <CAJTo0Lbkh11ucPqu1cJdEeXbjxRVt89TFpjt82xt_rfkXrFj=w@mail.gmail.com>
On 06/22/2015 06:14 PM, Burton, Ross wrote:
> On 22 June 2015 at 22:58, Philip Balister <philip@balister.org> wrote:
>
>> That said, it will be unsupported before the next release goes unsupported.
>>
>
> Exactly: a few months after 1.9 ships, Qt4 is officially dead. So the
> question remains, is Qt4 actually heavily used, or has everyone moved to
> Qt5 already? (note that both Qt3 and Qt5 are maintained in their own
> layers).
GNU Radio is still qt4. I am beating, but they are short GUI guys.
Philip
>
> Ross
>
next prev parent reply other threads:[~2015-06-22 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 10:43 Future of Qt4 recipes Burton, Ross
2015-06-22 14:27 ` Otavio Salvador
2015-06-22 21:48 ` Florian Boor
2015-06-22 21:58 ` Philip Balister
2015-06-22 22:14 ` Burton, Ross
2015-06-22 22:50 ` Philip Balister [this message]
2015-06-23 23:13 ` akuster808
2015-06-24 0:26 ` 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=5588914A.6020705@balister.org \
--to=philip@balister.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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