On 12/10/15, Philip Langdale <phil...@overt.org> wrote:
> On 2015-12-09 21:34, wm4 wrote:
>> On Mon, 7 Dec 2015 19:34:20 +0100
>> Timo Rothenpieler <t...@rothenpieler.org> wrote:
>>
>>> > I don't remember if this was discussed when avisynth and other headers
>>> > where included, but what's the advantage of directly including the
>>> > header and burden the FFmpeg sources, rather than asking the user to
>>> > download them in case of need?
>>>
>>> The nvenc sdk isn't exactly a common thing that distributions provide.
>>> As distributions can now easily ship ffmpeg with nvenc support, this
>>> propably helps users who now no longer need to build ffmpeg themselves
>>> for nvenc support.
>>
>> So why would distros build with nvenc support, if they can't even do a
>> simple thing like installing a single header file?
>>
>> Are we really talking about including a huge 3rd party header because
>> distros are so lazy? What's next, do we add Windows headers to the
>> FFmpeg tree, because MinGW lags severely behind the newest definitions
>> like HEVC DXVA support?
>>
>> We could just provide a download link for the nvenc header somewhere if
>> the problem is finding the header.
>
> Admittedly, we are solving someone else's problem, but the header is
> buried inside the SDK download which is hidden behind a click-through on
> nvidia's web page. So it's not made available in a way that is readily
> consumable by an end user or by a distribution vendor.
I have had some success scripting its download in the past, FWIW :)
Cheers!
-roger-
echo "installing nvenc [nvidia gpu assisted encoder]"
curl
http://developer.download.nvidia.com/assets/cuda/files/nvidia_video_sdk_6.0.1.zip
-O -L
unzip nvidia_video_sdk_6.0.1.zip
cp nvidia_video_sdk_6.0.1/Samples/common/inc/*
$mingw_w64_x86_64_prefix/include
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
