[FFmpeg-devel] [PATCH] configure: support static libnpp [v2]
andreas.hakon at protonmail.com
Fri Jun 2 14:51:06 EEST 2017
(repost without quotes... sorry!)
> I don't dispute that static linking might be useful, but I'm still not
> liking needing a separate configure option, if perhaps another
> solution can be found.
I'm glad if you point me in to another solution.
Meanwhile this solution is simple and effective.
> However, one thing to remember is that you need to build FFmpeg as
> non-free for this, so you are not allowed to distribute these
> binaries. So one might argue that when you need the CUDA SDK during
> build time, and you cannot distribute these binaries, then what
> advantage is there?
True. Non-free is required to be enabled. However, some advantages exists:
1) If you link libnpp* static (with this patch) you can upgrade the NVidia driver and the CUDA SDK without recompiling the FFmpeg. The main advantage is this.
2) If you link libnpp* static you can uninstall the CUDA SDK after compile the FFmpeg. It doesn't need the SDK to run. Then you can save (a lot of) space.
3) Even if you compile FFmpeg with "non-free" enabled, you can use the binary in any machine you own. You can't distribute the binary, but you can copy/use the binary. So, if you have a cluster of machines, you only need to copy the binary, install the NVidia driver, and... nothing more. The CUDA SDK is not a requirement for run FFmpeg, only to compile it.
You agree with these advantages?
More information about the ffmpeg-devel