On Sun, May 18, 2014 at 5:15 AM, Anton Khirnov <[email protected]> wrote: > > Another issue that arises in relation with this patch is that the muxer uses > an > avpriv_ function to parse the extradata before writing it to the file. This > function takes an AVCodecContext and reads the extradata from there. > If we want to avoid modifying the stream codec context, we must change this > function. However, that would break compatibility between mismatched old/new > lavf/lavc combinations. > > Which brings us to the larger class of issues associated with avpriv_. Should > we > export them all as some kind of proper public API? Or should we accept some > people's suggestion to forbid mismatched library versions?
I think it would be better to export the avpriv_ function to some kind of public API (or a whole new library maybe, libavbridge?). In this way lavc and lavf would be less tied together and we could hope for the utiopian situation where every library calls the other through public api only. Forbidding mismatched library versions I fear would be somewhat difficult and not completely clean and would not save a lot of coding time, imho. Cheers, -- Vittorio _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
