All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: Re: [oe] GStreamer 0.10's future
Date: Sat, 10 May 2014 13:37:59 +0200	[thread overview]
Message-ID: <lkl32n$3qq$1@ger.gmane.org> (raw)
In-Reply-To: <CAJTo0LZJ-cLjvGH5YZA1Tu-Wz6biKn=A2mVp5rrkwzkFB-ggTg@mail.gmail.com>

Sounds like a good idea.

Am 09.05.2014 21:22, schrieb Burton, Ross:
> On 9 May 2014 16:19, Neuer User <auslands-kv@gmx.de> wrote:
>> Yes, it does, as long as you need QtMultimedia. Same applies to Qt5.
>> There was a discussion on the Qt mailing list about moving to
>> gstreamer1.0, but this seems to be rather some time in the future was my
>> impression.
> 
> So Qt 5.3 won't have GStreamer 1.0 support.  The port is being done in
> a branch so it's possible that it will land in Qt 5.4, which is due to
> be released in the September/October timeframe.
> 
> One option would be to move GStreamer 0.10 into another layer, give
> Qt4/Qt5 disabled-by-default GStreamer 0.10 options and hope that by
> the time Yocto 1.7 is released, Qt5.4 with GStreamer 1.0 is also
> released.  Even as someone who's rather keen on removing cruft from
> oe-core that's a bit too eager for my liking.
> 
> Revised plan unless anyone has a better idea: in 1.7 we'll move
> everything possible away from GStreamer 0.10 but keep 0.10 around
> until the 1.8 cycle, and then revisit the Qt situation.
> 
> Ross
> 




  reply	other threads:[~2014-05-10 11:38 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 14:48 GStreamer 0.10's future Burton, Ross
2014-05-08 15:02 ` Koen Kooi
2014-05-08 15:02   ` [OE-core] " Koen Kooi
2014-05-08 15:07 ` Paul Eggleton
2014-05-08 15:07   ` [OE-core] " Paul Eggleton
2014-05-08 15:14   ` Burton, Ross
2014-05-08 15:14     ` [OE-core] " Burton, Ross
2014-05-08 16:04   ` Tim Orling
2014-05-08 16:04     ` [OE-core] " Tim Orling
2014-05-08 16:19   ` [yocto] " Martin Jansa
2014-05-08 16:19     ` [OE-core] " Martin Jansa
2014-05-08 16:19     ` [yocto] " Martin Jansa
2014-05-08 16:57     ` [yocto] " Paul Eggleton
2014-05-08 16:57       ` [OE-core] " Paul Eggleton
2014-05-08 16:57       ` [yocto] " Paul Eggleton
2014-05-08 17:21       ` [yocto] " Martin Jansa
2014-05-08 17:21         ` [OE-core] " Martin Jansa
2014-05-08 17:21         ` [yocto] " Martin Jansa
2014-05-08 17:29         ` [yocto] " Paul Eggleton
2014-05-08 17:29           ` [OE-core] " Paul Eggleton
2014-05-08 17:29           ` [yocto] " Paul Eggleton
2014-05-08 22:06       ` [yocto] " Richard Purdie
2014-05-08 22:06         ` [OE-core] " Richard Purdie
2014-05-08 22:06         ` [OE-core] [yocto] " Richard Purdie
2014-05-08 15:11 ` Carlos Rafael Giani
2014-05-08 15:25   ` Burton, Ross
2014-05-08 15:54 ` Burton, Ross
2014-05-09 15:19   ` Neuer User
2014-05-09 15:19     ` [oe] " Neuer User
2014-05-09 18:47     ` [yocto] " Burton, Ross
2014-05-09 18:47       ` Burton, Ross
2014-05-09 18:47       ` [yocto] " Burton, Ross
2014-05-09 19:22     ` [yocto] [oe] " Burton, Ross
2014-05-09 19:22       ` Burton, Ross
2014-05-09 19:22       ` [yocto] " Burton, Ross
2014-05-10 11:37       ` Neuer User [this message]
2014-05-10 16:14 ` Khem Raj
2014-05-10 16:14   ` [OE-core] " Khem Raj

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='lkl32n$3qq$1@ger.gmane.org' \
    --to=auslands-kv@gmx.de \
    --cc=yocto@yoctoproject.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 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.