Recently migrated fom 2.3 to 3.0 .
Can't say that that was extreemly easy, but there is a clearly defined way:
Can't say that that was extreemly easy, but there is a clearly defined way:
- read static assertions after compiling
- see comments over the deprecated funtions
for my usage of libavcodec + swscale it helped . But there was some old ugly hack for swscale, and some bugs with broken video appeared during the testing (thank god it was automated). So I had to remove this hack and use swscale simply by the api.
So: static assertions and comments solve the problem of migrating, it was even more convenient then some pdf or html document, because I could use the redirection of IDE. But it left feeling, that I probably missed something and don't even know it.
for my usage of libavcodec + swscale it helped . But there was some old ugly hack for swscale, and some bugs with broken video appeared during the testing (thank god it was automated). So I had to remove this hack and use swscale simply by the api.
So: static assertions and comments solve the problem of migrating, it was even more convenient then some pdf or html document, because I could use the redirection of IDE. But it left feeling, that I probably missed something and don't even know it.
Looks like for such a big project to make comprehensive documentation is a quite a big task.
--
С уважением,
Слободенюк Александр Игоревич
контактный телефон: +7-925-050-64-62
19.06.2016, 01:44, "salsaman" <[email protected]>:
,On Sat, Jun 18, 2016 at 4:40 PM, Ben Woods <[email protected]> wrote:On 18 June 2016 at 17:23, salsaman <[email protected]> wrote:Salsaman.Regards,Creating a migration guide is standard practice when changing the major version of a well used library API.Code examples only provide solutions for specific implementation details.
Is there really no documentation anywhere ? That seems to defeat the purpose of providing a usable library.I second that. FreeBSD is still going through the motions of trying to update numerous open source software packages to use the newest API. And there are plenty which have not yet done it themselves, and therefore require manual patching. We use patches from Linux distributions when they are available, but some are not and we work it out from examples.I believe that a good API documentation should not just explain what is available in each version, but what has changed since the last version and the recommended alternative.Regards,BenFor reference, here is an example of what I consider to be good migration documentation:Gabriel._______________________________________________
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
