ping
Will push in 2 days if nobody objects.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Wed, 19 Oct 2016 14:00:29 +0200
Timo Rothenpieler wrote:
> ---
> compat/cuda/dynlink_cuda.h | 88 +
> compat/cuda/dynlink_cuviddec.h | 808
> +
> compat/cuda/dynlink_loader.h | 254 +
> compat/cuda/dynlink_nvcuvid.h | 316 +
On 19.10.2016 21:41, Sven C. Dack wrote:
> You are misinterpreting it. The FAQ explicitly excludes external
> components such as compilers, kernels and libraries.
What is or is not a system component is quite debatable.
However, it always depends on the specific operating system under
consideratio
On 19/10/16 20:23, Andreas Cadhalpun wrote:
Read the FAQ: "What about the compiler, the toolchain?"
Best regards,
Andreas
1: http://gpl-violations.org/faq/sourcecode-faq/
You are misinterpreting it. The FAQ explicitly excludes external components such
as compilers, kernels and libraries.
On 19.10.2016 20:46, Sven C. Dack wrote:
> No. This is exactly what I meant with wearing tin foil hats.
Insults won't help you.
> Just because a compiler includes information provided by header
> files into the compilation process does this not imply a transfer
> of ownership or copyright of this
On 19/10/16 18:56, Andreas Cadhalpun wrote:
I think you are missing the main problem here: FFmpeg is licensed
under the LGPL 2.1, which states [1]:
" 4. You may copy and distribute the Library [...] in object code
or executable form [...] provided that you accompany it with the
complete correspo
On 19.10.2016 18:52, Sven C. Dack wrote:
> On 19/10/16 17:18, Hendrik Leppkes wrote:
>> Thats the general interpretation of the license situation. If you
>> include non-free headers, your binary becomes non-free, hence why
>> building with cuda currently requires the --enable-nonfree option.
> No.
On 19/10/16 17:18, Hendrik Leppkes wrote:
Thats the general interpretation of the license situation. If you
include non-free headers, your binary becomes non-free, hence why
building with cuda currently requires the --enable-nonfree option.
No. This is a generalization and cannot make sense. At b
On Wed, Oct 19, 2016 at 6:07 PM, Sven C. Dack wrote:
> On 19/10/16 15:25, Hendrik Leppkes wrote:
>>
>> You seem to be referring to the license of the cuvid files, which is
>> not the license actually used by the CUDA headers. The CUDA headers
>> are under a full proprietary license with no such pe
On 19/10/16 15:25, Hendrik Leppkes wrote:
You seem to be referring to the license of the cuvid files, which is
not the license actually used by the CUDA headers. The CUDA headers
are under a full proprietary license with no such permission.
Are you saying the use of CUDA header files (with #inc
On Wed, Oct 19, 2016 at 3:32 PM, Sven C. Dack wrote:
> On 19/10/16 13:50, Hendrik Leppkes wrote:
>>
>> On Wed, Oct 19, 2016 at 2:00 PM, Timo Rothenpieler
>> wrote:
>>>
>>> ---
>>> compat/cuda/dynlink_cuda.h | 88 +
>>> compat/cuda/dynlink_cuviddec.h | 808
>>> +
>> +/*
>> + * This file is part of FFmpeg.
>> + *
>> + * FFmpeg is free software; you can redistribute it and/or
>> + * modify it under the terms of the GNU Lesser General Public
>> + * License as published by the Free Software Foundation; either
>> + * version 2.1 of the License, or (at your optio
On 19/10/16 13:50, Hendrik Leppkes wrote:
On Wed, Oct 19, 2016 at 2:00 PM, Timo Rothenpieler
wrote:
---
compat/cuda/dynlink_cuda.h | 88 +
compat/cuda/dynlink_cuviddec.h | 808 +
compat/cuda/dynlink_loader.h | 254 +
compat/cud
On Wed, Oct 19, 2016 at 2:00 PM, Timo Rothenpieler
wrote:
> ---
> compat/cuda/dynlink_cuda.h | 88 +
> compat/cuda/dynlink_cuviddec.h | 808
> +
> compat/cuda/dynlink_loader.h | 254 +
> compat/cuda/dynlink_nvcuvid.h | 316 +
---
compat/cuda/dynlink_cuda.h | 88 +
compat/cuda/dynlink_cuviddec.h | 808 +
compat/cuda/dynlink_loader.h | 254 +
compat/cuda/dynlink_nvcuvid.h | 316
4 files changed, 1466 insertions(+)
create mode 100644 compat/
15 matches
Mail list logo
