- Ffmpeg windows lgpl software#
- Ffmpeg windows lgpl code#
- Ffmpeg windows lgpl license#
- Ffmpeg windows lgpl download#
- Ffmpeg windows lgpl free#
I know there is an "Archives" directory that stores a couple of weeks of git releases, but now the links listed below download a file which contains the build date in the filename. It would be greatly appreciated if the link to the file that downloads does not contain the build date. I have an automated procedure that downloads the latest "full" build and extracts the compressed file and updates the main program files. But it is a trick that can get around this GPL license.I have a request. Still, be aware that you might need some legal advise here.
Ffmpeg windows lgpl code#
THE GPL code and non-GPL code would be two different programs if used this way.
Ffmpeg windows lgpl license#
It is a trick to get around the license restriction but since the interface is yours and yours only, the GPL will be blocked by it. The interface will also serve as a solution to change the GPL code by a different solution. Your own code would never be GPL since it's not using any GPL code directly. This wrapper library will serve as a protection buffer between your own propriety code and the GPL code. It's 100% your own code and you could use the same interface to connect to a different library. However, although it would expose your interface to the outside world, your interface cannot be contaminated. This library would fall under the GPL license and thus it gets contaminated. Next, create a wrapper library around the GPL code which will also implement your personal interface. Since this interface is your own creation, it would fall under your own license.
However, there's nothing wrong with using a similar structure. Don't re-use anything from the GPL code because that would fall under the GPL license. This will be used between your application and a separate library that you will be creating. Still, there is a way to get around it.įirst, start by defining your own interface to send over data. What makes it worse is how contagious it can be. In general, it's one of the few things that I consider to be real nasty of the GPL. So the question is: can I use it like I'm doing right now or will I be executed by an army of lawyers? I would have made my project LGPL as well and released the source, but this is not up to me. I am really confused by all this legal things.
Ffmpeg windows lgpl software#
I do not change it, I only use a built version of the software for windows. P.StartInfo = new ("lgplSoftware.exe", myParams) To do so, I only call it in my software as such: p = new () I want to use a tool ( ffmpeg) that is under GNU Lesser General Public License, version 2.1 GNU General Public License (GPL) version 2 for some components. Including a link to the upstream project is not sufficient (at least for version 2 of the GPL). For example, if you package up your application in an installer and include copies of GPL'ed or LGPL'ed executables in the installer, then you're distributing LGPL'ed or GPL'ed code and must make copies of the source code available (either online, by mail-in offer, or by CD, depending on how you distribute your app).
(And it's probably time to consult your lawyer to find out for sure.)Īlso, although you didn't specifically ask about this, keep in mind that distributing GPL'ed or LGPL'ed software with your software means that you're required to include a copy of the license with your installer and to also distribute the source code. The GPL does require that proprietary and GPL'ed programs "are not combined in a way that would make them effectively a single program." If your program is completely dependent upon GPL'ed executables, such that it wouldn't be usable without them even though it is a standalone binary, then that might place you on shakier ground. (Otherwise, we couldn't run any GPL'ed software under Windows.)
Ffmpeg windows lgpl free#
(This is what the GPL FAQ is talking about by "communicat at arms length.") This doesn't even violate the spirit of the LGPL and GPL they tolerate the existence of proprietary software and assume that at some point proprietary programs will spawn free programs and vice versa. Your users are free to use that binary themselves for its authors' intended purposes and are free to download and compile the source themselves, so all of their freedoms are preserved, and you're not in violation of the GPL or LGPL. You're not linking GPL'ed or LGPL'ed code at all, you're only spawning a GPL'ed or LGPL'ed binary, and the GPL and LGPL permit this. Linking has a specific meaning in computer programming. Using gpl software in commercial products
0 kommentar(er)
