current opencv[ffmpeg] feature makes the whole opencv library to be GPL licensed? #19334
Labels
category:port-feature
The issue is with a library, which is requesting new capabilities that didn’t exist
FFmpeg uses LGPL license by default which is pretty permissive when it comes to building a commercial software that uses ffmpeg as its part.
This gives a good summary:
https://www.ffmpeg.org/legal.html
This is helpfull for whoever is going to take care of this issue, it provides a list of parts in ffmpeg which require GPL license:
https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/refs/heads/master/LICENSE.md
Unfortunately when one builds opencv[ffmpeg], ffmpeg package by default is configured to be with GPL license. I am pretty sure it is because with --enable-gpl more filters are included which makes ffmpeg more usable.
But here it comes:
https://www.gnu.org/licenses/gpl-faq.html#IfLibraryIsGPL
Anything linked against GPL becomes itself a GPL. And so on till the user's code itself. Which is absolutely not the thing that commercial developer wants to have. And being sure that opencv itself has always BSD or Apache2.0 license could be quite an illusion as we see from the case above.
I suggest changing ffmpeg configuration when user does
vcpkg install opencv[ffmpeg]
to be non-GPL by default.How can I manually change ffmpeg package configuration that opencv defines?
I would say there could be a nice feature to check resulting licensing for every package installed based on individual licenses of dependant packages.
The text was updated successfully, but these errors were encountered: