All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neuer User <auslands-kv@gmx.de>
To: openembedded-devel@lists.openembedded.org
Cc: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: GStreamer 0.10's future
Date: Fri, 09 May 2014 17:19:36 +0200	[thread overview]
Message-ID: <536CF208.3000400@gmx.de> (raw)
In-Reply-To: <CAJTo0LZ_S=mNgM6gtPSfYf=AVRxdLcJ_CO31c+emmQrib80hjw@mail.gmail.com>

Am 08.05.2014 17:54, schrieb Burton, Ross:
> On 8 May 2014 15:48, Burton, Ross <ross.burton@intel.com> wrote:
>> For the 1.7 release I want to move GStreamer 0.10 from oe-core into
>> meta-multimedia, and ensure everything in oe-core has ported to
>> GStreamer 1.x.  GStreamer 0.10 is considered dead upstream and is
>> unmaintained so we don't need to be shipping both versions anymore.
> 
> So the catch here is that Qt4 currently depends on GStreamer 0.10.
> 
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.

> Can someone who doesn't come out in a rash when looking at C++ code
> spend two minutes to tell if me Qt4 supports GStreamer 1.0 (unlikely)
> and whether we can make GStreamer 0.10 support a build-time
> configuration and simply disable it in oe-core.
> 
> Ross
> 




WARNING: multiple messages have this Message-ID (diff)
From: Neuer User <auslands-kv@gmx.de>
To: openembedded-devel@lists.openembedded.org,
	 OE-core <openembedded-core@lists.openembedded.org>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [oe] GStreamer 0.10's future
Date: Fri, 09 May 2014 17:19:36 +0200	[thread overview]
Message-ID: <536CF208.3000400@gmx.de> (raw)
In-Reply-To: <CAJTo0LZ_S=mNgM6gtPSfYf=AVRxdLcJ_CO31c+emmQrib80hjw@mail.gmail.com>

Am 08.05.2014 17:54, schrieb Burton, Ross:
> On 8 May 2014 15:48, Burton, Ross <ross.burton@intel.com> wrote:
>> For the 1.7 release I want to move GStreamer 0.10 from oe-core into
>> meta-multimedia, and ensure everything in oe-core has ported to
>> GStreamer 1.x.  GStreamer 0.10 is considered dead upstream and is
>> unmaintained so we don't need to be shipping both versions anymore.
> 
> So the catch here is that Qt4 currently depends on GStreamer 0.10.
> 
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.

> Can someone who doesn't come out in a rash when looking at C++ code
> spend two minutes to tell if me Qt4 supports GStreamer 1.0 (unlikely)
> and whether we can make GStreamer 0.10 support a build-time
> configuration and simply disable it in oe-core.
> 
> Ross
> 




  reply	other threads:[~2014-05-09 15:20 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 [this message]
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       ` [oe] " Neuer User
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=536CF208.3000400@gmx.de \
    --to=auslands-kv@gmx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --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.