On Tue, 20 Dec 2016 16:04:47 +0100 Nicolas George <[email protected]> wrote:
> Le decadi 30 frimaire, an CCXXV, wm4 a écrit : > > Well, what do you want to work towards? I'd say either split the git > > repo > > There is a lot of work before that: > > ~/tmp/git/libav $ git grep avpriv | wc -l > 960 True. > Can somebody explain what the separation between libraries is good for > anyway? As a means to enforce good modularization. Also makes a lot of sense from the point of view of people who use only some of the sub-libraries, instead of the whole "framework". E.g. if you use libavcodec only, you don't want any hidden dependencies on libavformat or any of the other libs. Personally I wouldn't mind if all the sub-libraries got merged into one library (at linking stage). But the status quo is kind of annoying from the point of view of a maintainer of an application that uses libav*. > I can see the benefit of organizing code in separate directories, of > course, but separating the libraries only bring headaches to users and > developers. What am I missing? Well, the idea is that if the split is done, it would actually make sense to treat them as separate libraries. The result would be no worse than with any other libraries. In theory. It would also require making ffmpeg.c/avconv.c a separate library, which would introduce FFmpeg and Libav developers to the pain of being an actual libav* API user. (Dealing with all those deprecations without just depending on git master versions of the sub-libs.) _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
