On Thu, May 30, 2019 at 04:39:46PM -0000, Tim Smith via OpenOCD-devel wrote: > We wanted to utilize OpenOCD as a DLL in-process in our application and > utilize its functionality, instead of keeping it in a seperate process and > utilize services. I was told their GPL prevents us from doing this, even if > we do or do not distribute our tools externally?. Is this true?.
The GPLv2 license says "You may modify ... and copy and distribute ... provided that you ...". The GPLv3 says "You may convey ... provided that you ..." and defines "convey" as "any kind of propagation that enables other parties to make or recieve copies". Are the people who have access to the computers running your application "other parties"? The FFmpeg documentation contains the following paragraph for a similar situation: "There are certain libraries you can combine with FFmpeg whose licenses are not compatible with the GPL and/or the LGPL. If you wish to enable these libraries, even in circumstances that their license may be incompatible, pass `--enable-nonfree` to configure. But note that if you enable any of these libraries the resulting binary will be under a complex license mix that is more restrictive than the LGPL and that may result in additional obligations. It is possible that these restrictions cause the resulting binary to be unredistributable." Best regards, Daniel _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
