James Almer (12020-11-13): > This results in a libavfilter binary that links to libvmaf for no reason, > potentially bloating it if it was linked statically.
That is not how static linking works. Static linking takes in the library exactly the object files required by the binary and other object files, nothing more. We could have -lqt -lwebkit2gtk on the link command, the linker would just observe that nothing in them is needed and ignore them. By the way, if the objections I got against merging the libraries (I don't remember exactly from whom) were based on this kind of misconception, it would be a good idea to revise them. On the other hand, it makes a difference with dynamic linking: the binary would be unable to run without the shared library present. Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
