Re: [FFmpeg-devel] [PATCH 1/5] configure: Add an explicit check and option for nvcc

2019-02-26 Thread Tobias Rapp
On 26.02.2019 21:36, Soft Works wrote: From: Jean-Baptiste Kempf Sent: Dienstag, 26. Februar 2019 15:01 [...] I don't think nvcc fit the"normally distributed with the operating system". I'm not sure if the role of nvcc has been fully understood. nvcc is some kind of 'pre-compiler' which is

Re: [FFmpeg-devel] [PATCH 1/5] configure: Add an explicit check and option for nvcc

2019-02-26 Thread Soft Works
> From: Jean-Baptiste Kempf > Sent: Dienstag, 26. Februar 2019 23:07 > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] [PATCH 1/5] configure: Add an explicit check and > option for nvcc > > On Tue, 26 Feb 2019, at 21:26, Soft Works wrote: > > It's an exte

Re: [FFmpeg-devel] [PATCH 1/5] configure: Add an explicit check and option for nvcc

2019-02-26 Thread Jean-Baptiste Kempf
On Tue, 26 Feb 2019, at 21:36, Soft Works wrote: > I'm not sure if the role of nvcc has been fully understood. > nvcc is some kind of 'pre-compiler' which is not distributed or linked to. > > Distributing GPL code that was compiled with MSVC doesn't require the > MSVC compiler to be open source as

Re: [FFmpeg-devel] [PATCH 1/5] configure: Add an explicit check and option for nvcc

2019-02-26 Thread Jean-Baptiste Kempf
On Tue, 26 Feb 2019, at 21:26, Soft Works wrote: > It's an external and separate executable. It is not a violation of > the GPL if ffmpeg checks for existence and executes that in a separate > process. Believing that executing in a separate process removes the obligation of the GPL is an very-muc

Re: [FFmpeg-devel] [PATCH 1/5] configure: Add an explicit check and option for nvcc

2019-02-26 Thread Soft Works
> From: Jean-Baptiste Kempf > Sent: Dienstag, 26. Februar 2019 15:01 > > [...] > > I don't think nvcc fit the"normally distributed with the operating system". I'm not sure if the role of nvcc has been fully understood. nvcc is some kind of 'pre-compiler' which is not distributed or linked to. Di

Re: [FFmpeg-devel] [PATCH 1/5] configure: Add an explicit check and option for nvcc

2019-02-26 Thread Soft Works
> From a technical standpoint, this whole series looks fine to me. > > However, it really does not fell non-nonfree to me that the only way to > build these filters remains to register with nvidia, accept their > various EULAs and download their SDK for nvcc and the libs around it. > > Even moving

Re: [FFmpeg-devel] [PATCH 1/5] configure: Add an explicit check and option for nvcc

2019-02-26 Thread Jean-Baptiste Kempf
Hello, On Tue, 26 Feb 2019, at 14:51, Timo Rothenpieler wrote: > > Note that, unlike the cuda_sdk dependency, using nvcc to compile > > a kernel does not cause a build to become non-free. Although nvcc > > is distributed with the cuda sdk, and is EULA encumbered, the > > compilation process we use

Re: [FFmpeg-devel] [PATCH 1/5] configure: Add an explicit check and option for nvcc

2019-02-26 Thread Timo Rothenpieler
On 21.02.2019 04:57, Philip Langdale wrote: The use of nvcc to compile cuda kernels is distinct from the use of cuda sdk libraries and linking against those libraries. We have previously not bothered to distinguish these two cases because all the filters that used cuda kernels also used the sdk.

[FFmpeg-devel] [PATCH 1/5] configure: Add an explicit check and option for nvcc

2019-02-20 Thread Philip Langdale
The use of nvcc to compile cuda kernels is distinct from the use of cuda sdk libraries and linking against those libraries. We have previously not bothered to distinguish these two cases because all the filters that used cuda kernels also used the sdk. In the following changes, I'm going to remove