Re: gst-ffmpeg is broken since the libav-9 introduction

[Mike Looijmans <mike.looijmans@topic.nl>]

On 09-03-15 16:26, Burton, Ross wrote:
> Oh and FWIW the Sato images in master just flipped from GStreamer 0.10
> to 1.4 by default, so I do hope that GStreamer 0.10 will disappear from
> oe-core after the next release (moving to meta-multimedia).
>
> Can I ask why you're still using GStreamer 0.10?  If there's a good
> reason to keep 0.10 in oe-core during the next cycle we can, but
> otherwise the sooner it can be removed entirely as it's no longer tested
> the better.

It works, and we're stuck with vendors providing no support for 1.x, and 
we've been trying to get the 1.x version integrated but that's a rather 
big task and the total lack of decent "how to migrate from 0.1 to 1.x" 
guides isn't doing much to speed that up either.

The current situation is so bad (and has been for many years) that we 
have our own copies of the gstreamer 0.1 recipes in OpenPLi.


> Ross
>
> On 9 March 2015 at 15:24, Burton, Ross <ross.burton@intel.com
> <mailto:ross.burton@intel.com>> wrote:
>
>
>     On 6 March 2015 at 17:51, Mike Looijmans <mike.looijmans@topic.nl
>     <mailto:mike.looijmans@topic.nl>> wrote:
>
>         Commit 4ceff7d0a1f28eb1ce5d288111015b__ff8d5e9a7e "libav: drop
>         older 0.8.* and use libav-9 by default" removed libav 0.8 in
>         favor of the "9" edition. However, after compiling this for a
>         MIPS box, the gst-ffmpeg plugin now refuses to load and displays
>         the following at runtime:
>
>
>     Hm, bad testing, sorry.  This would be why gstreamer-libav 1.0
>     defaults to using it's own internal copy of libav then. :/
>
>     I see that gstreamer-ffmpeg_0.10 defaults to using the internal
>     libav, and as the API clearly changed we need to do that.  Can you
>     verify that removing external-libav from the PACKAGECONFIG fixes
>     this problem?
>
>     Ross
>
>


-- 
Mike Looijmans