On 21 September 2016 at 14:38, Philip Langdale <phil...@overt.org> wrote:
> The cuvid header situation is a mess - the only feature-complete headers > are > in the Video SDK and not in the cuda header collection. The headers in the > Video SDK are MIT licenced, and so we can bundle them like we do the nvenc > header. > > Once bundled, we do need to tweak them to remove the use of a dynlink > system that's specific to the Video SDK samples, which we don't need and > don't really want. > Does using the MIT headers instead effect the current licensing constraints on cuvid (as its nonfree at present). I was just wondering if keeping in the dynlink_cuda stuff could be used to remove the cuda compile dependency and actually allow cuvid compiles to be distributed. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
