[FFmpeg-devel] Discussion of all-inclusive full stack builds

Tim Jones tolistim at gmail.com
Sun May 12 21:52:03 EEST 2019


Hi Folks,

I've long been a fanatic for ffmpeg and now have the bandwidth to dip my toes into the developer pool.  My primary experience is in file I/O in C, C++ , and Python, and I force my team to pay close attention to smaller-is-better refactoring.

With the enormous number of config options, newcomers to the development side of things (yes, that means me, too) can find the inclusion of a specific capability to be quite daunting (and I've been coding since before autoconf existed).

Has anyone previously discussed or offered up a simplified set of config macros for something like:

--disable-all-proprietary/--enable-all-proprietary

I have run into situations where I've needed to recompile to meet a specific situation that could have been easily handled by simply enabling everything - regardless of it's status as FOSS or proprietary.

If such a build level were created, would there be a recognizable performance hit with such an option?

--
Tim



More information about the ffmpeg-devel mailing list