Quoting Anton Khirnov (2022-08-06 15:15:58) > Quoting Andreas Rheinhardt (2022-08-06 13:50:37) > > rcombs: > > > This is fully backwards-compatible in both ABI and API, > > > so it's only a minor bump. > > > > It is not fully backwards-compatible API-wise: If you use a function > > pointer for swr_alloc_set_opts2 by hardcoding its type, you will get > > warnings now (or even errors depending upon your -Werror; it is an error > > by default for C++). Given that I do not know about other language > > bindings I have so far refrained from applying > > https://patchwork.ffmpeg.org/project/ffmpeg/patch/as1pr01mb95649a21f5f9a45d40e6ac1d8f...@as1pr01mb9564.eurprd01.prod.exchangelabs.com/ > > This does not mean that I block your patch; to the contrary: If it > > breaks nothing, I will apply the above patch after a month or so. > > Maybe now could be a good time for a major bump, since we just had a > release. It's also been two releases since the last one.
I would also love to finally get rid of FF_API_THREAD_SAFE_CALLBACKS -- Anton Khirnov _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
