3 ms·
Imagine if a user optionally could compile ffmpeg with only the code that the user will actually need. For example, a user might only use one or a few formats
by 1vuio0pswjnm7 4y ago
Imagine if a user optionally could compile ffmpeg with only the code that the user will actually need. For example, a user might only use one or a few formats in practice and only a handful of commands for a limited number of tasks. Configure scripts often allow users to accomplish this to some extent, e.g., excluding libraries we know we'll never use. Another idea is that ffmpeg could output C source code that would assist with compiling a "single purpose" executable. Something similar to tcpdump -dd or curl --libcurl. (How many folks actually use those options, not sure, but they still exist.)
It's common to see comments from ffmpeg users where they have devised some certain command line that accomplishes some specific task but who otherwise do not routinely use ffmpeg for much else. If these folks were able to compile an application that performed only this task using only the required ffmpeg libraries, would this be smaller and less complicated than an ffmpeg static binary.
- dnadler 4y agoI feel like asking people to compile it to have fewer options would be a lot more complicated than just having them run it with the options they need, no?
- Am4TIfIsER0ppos 4y agoForgive me if I missed some sort of joke but you can do exactly that. Don't need the hevc decoder? disable it. Only need the hevc decoder? disable everything and enable only it. That is a compile time option but if you're not using the system ffmpeg libs then I guess you'd be compiling it anyway.
- 1vuio0pswjnm7 4y agoYou are forgiven. It's easy to misinterpret online comments.