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. Regards, Salsaman. http://lives-video.com https://www.openhub.net/accounts/salsaman On Sat, Jun 18, 2016 at 11:44 AM, Carl Eugen Hoyos <[email protected]> wrote: > Axel Holzinger <aholzinger@...> 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 > [email protected] > http://ffmpeg.org/mailman/listinfo/libav-user >
_______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
