Re: [yocto] [oe] GStreamer 0.10's future

2014-05-10 Thread Neuer User
Sounds like a good idea.

Am 09.05.2014 21:22, schrieb Burton, Ross:
 On 9 May 2014 16:19, Neuer User auslands...@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
 


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [oe] GStreamer 0.10's future

2014-05-09 Thread Neuer User
Am 08.05.2014 17:54, schrieb Burton, Ross:
 On 8 May 2014 15:48, Burton, Ross ross.bur...@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
 


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [oe] GStreamer 0.10's future

2014-05-09 Thread Burton, Ross
On 9 May 2014 16:19, Neuer User auslands...@gmx.de wrote:
 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.

Oh, even Qt5 needs 0.10?  That's disappointing.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [oe] GStreamer 0.10's future

2014-05-09 Thread Burton, Ross
On 9 May 2014 16:19, Neuer User auslands...@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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto