Le duodi 12 ventôse, an CCXXIII, Gupta, Maneesh a écrit : > I see a lot of modules that are autodetected. And not all of them are > system libs.
The consensus is this: A. A library that is redundant with a native implementation of a FFmpeg target feature (target = implementing multimedia codecs formats, protocols , devices and filters) should not be automatically enabled (example: libvorbisdec). Z. A system library that is necessary for an important target feature of FFmpeg should be automatically enabled (example: zlib). There are a lot of steps between these two extreme cases, including: B. A library that overlaps a FFmpeg target feature but is not redundant with the native implementation (being significantly better in some way) (example: libopenjpeg IIRC, libvorbisenc). C. A library that overlaps FFmpeg target features that is currently not implemented natively (example: libx264, libopusenc). W. A more-or-less system library that is necessary for a more-or-less useful target feature of FFmpeg (example: SDL, Freetype Everyone has their own opinion of the correct place for the limit. Feel free to ignore comments that try to pass their own opinion as the official project policy. The official project policy is "somewhere between A and Z". (My personal opinion is that it should be itself a configure option: ./configure --enable-auto-all, ./configure --enable-auto-useful...) Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
