[FFmpeg-devel] [PATCH] News: Removal of libndi

Jean-Baptiste Kempf jb at videolan.org
Mon Mar 25 19:02:43 EET 2019


On Mon, 25 Mar 2019, at 08:32, Tobias Rapp wrote:
> > Most of those hardware libraries are glorified ioctls around the driver and shipped with the drivers.
> > And I see this with nVidia, Intel MFX and Decklink (lots of "acquire C++ interface, set param" there, release the C++ interface).
> > 
> > Matrox seems to do something else, though, introducing a special library for FFmpeg consumption, and I doubt that feels like a driver...
> 
> The GPL is mentioned a lot in this thread. Maybe it would make sense to 
> distinguish the two cases where FFmpeg is compiled with --enable-gpl and 
> without it -- as the LGPL applies in that case.

That does not change a thing, sorry.
The section 6 of the LGPLv2.1 is similar to the section 3 of the GPL, and mentions exactly the same limitations and exceptions for major components of the OS.

The fact that you can combine the library with a 3rd party library inside your program does not allow you to ship non-LGPL-compatible code inside the library. (The library must be changeable + redistributable by the user).

I know that means that you can do more or less the same feature, but that means the architecture must be different.



-- 
Jean-Baptiste Kempf -  President
+33 672 704 734


More information about the ffmpeg-devel mailing list