Although that might be that they just push the responsibility down on the software developer/company who distributes their application with chromium.Īpparently ffmpeg has a checklist of how to be licence compliant. I did a lot of research and I found out the followings:įfmpeg is shipped with chromium, they built their own version of ffmpeg and it seems they also have licence for it. How do I compile/build electron to make it licence compatible (in case its not?).Am I legally able to still distribute the application and be licence-compliant with ffmpeg without owning any proper licence to it? I thought chromium dealt with the licencing on this topic since so many applications nowadays are shipped with using electron and chromium under the hood.It came to my attention that ffmpeg is shipped with electron, which has GPL/LGPL licence. You must take these into consideration too.Recently I'm working on an electron based application that is free to use but also has subscription based services. FFmpeg especially when used in a commercial software package. So based on all I said above, it depends on how you interact with FFmpeg.Īnd in all cases whether using the GPL or LGPL regardless of how you call FFmpeg you will need to redistribute the source of FFmpeg proper.Īs a side note, there are also codec patents to consider wrt.
I want to bundle a built (.exe) copy FFMPEG, which is licensed under GPL 2, with my own software.But I don't want to have to open source my software project. This does not sound a correct assumption to me, but there is not enough specifics in your question to be sure. My understanding is that the GPL 2 licensed component does not affect my software if it is compiled/built - it would affect it if I was including some/all of the source code in my own project. Say you use FFmpeg as-is, unmodified and call its command line tool in a subprocess, then in most cases neither a GPL nor an LGPL copyleft would back to the code that spawns the subprocess. In all cases, the details of which L/GPL version is in play and how you interact with FFmpeg matters a lot. If the library is LGPL-licensed then then LGPL copyleft terms would flow back and apply to the calling code is you use some static linking and would not apply if you use dynamic linking. If the library is GPL-licensed then then GPL copyleft terms would flow back and apply to the calling code.
Second, if you link with and call the libav* libraries from your proprietary code, the general community opinion is that you may eventually create some kind of derived of the library. First FFmpeg can be built with different licensing depending on the build config resulting in binaries that are LGPL or GPL-licensed, but not always GPL-licensed.
0 kommentar(er)
