[Libav-user] API changes v2.8.x ==> 3.0.x

salsaman salsaman at gmail.com
Sat Jun 18 17:23:38 CEST 2016

Creating a migration guide is standard practice when changing the major
version of a well used library API.
Is there really no documentation anywhere ? That seems to defeat the
purpose of providing a usable library.

Code examples only provide solutions for specific implementation details.



On Sat, Jun 18, 2016 at 11:44 AM, Carl Eugen Hoyos <cehoyos at ag.or.at> wrote:

> Axel Holzinger <aholzinger at ...> writes:
> > > Note that (major) parts of the 3.0 API are deprecated.
> >
> > But isn't the 3.0 API the newest one?
> No.
> I cannot answer how you have to change your code (and you
> did not provide any code that could be changed by readers)
> but both ffmpeg.c itself (or libavformat/*.c) and every open
> source software using FFmpeg had to be changed so it should
> be possible to find examples.
> Debian for example had to patch many packages to update to
> 3.0.
> Sorry, Carl Eugen
> _______________________________________________
> Libav-user mailing list
> Libav-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/libav-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ffmpeg.org/pipermail/libav-user/attachments/20160618/c51a7eb0/attachment.html>

More information about the Libav-user mailing list