On Dec 28, 2007 1:05 AM, Daniel Barkalow <barkalow@xxxxxxxxxxxx> wrote: > > It probably actually falls under the "system software" exception, in that > case (when distributing source, you have to include everything needed to > build the source, except for normal system software, which you can assume > the recipient has). > Reading the GPL FAQ at www.gnu.org I have come up with following clarifications that IMO apply to this case: http://www.gnu.org/licenses/gpl-faq.html#WindowsRuntimeAndGPL ------------------------------------------------------------------------------------------------- Q: I'm writing a Windows application with Microsoft Visual C++ (or Visual Basic) and I will be releasing it under the GPL. Is dynamically linking my program with the Visual C++ (or Visual Basic) run-time library permitted under the GPL? A: The GPL permits this because that run-time library normally accompanies the compiler or interpreter you are using. So it falls under the exception in GPL section 3. That doesn't mean it is a good idea to write the program so that it only runs on Windows. Doing so results in a program that is free software but "trapped" (in this case, trapped by Windows instead of by Java, but the effect is the same). (Historical note: As of December 2006 Sun is in the middle of rereleasing its Java platform under GNU GPL.) http://www.gnu.org/licenses/gpl-faq.html#GPLCompatInstaller ----------------------------------------------------------------------------------------- Q: I would like to bundle GPLed software with some sort of installation software. Does that installer need to have a GPL-compatible license? A: No. The installer and the files it installs are separate works. As a result, the terms of the GPL do not apply to the installation software. http://www.gnu.org/licenses/gpl-faq.html#NonFreeTools -------------------------------------------------------------------------------- Q: Can I release a program under the GPL which I developed using non-free tools? A: Which programs you used to edit the source code, or to compile it, or study it, or record it, usually makes no difference for issues concerning the licensing of that source code. However, if you link non-free libraries with the source code, that would be an issue you need to deal with. It does not preclude releasing the source code under the GPL, but if the libraries don't fit under the "system library" exception, you should affix an explicit notice giving permission to link your program with them. The FSF can give you advice on doing this. http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs ------------------------------------------------------------------------------------------ Q: What legal issues come up if I use GPL-incompatible libraries with GPL software? A: If the libraries that you link with fall within the following exception in the GPL: "However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable." then you don't have to do anything special to use them; the requirement to distribute source code for the whole program does not include those libraries, even if you distribute a linked executable containing them. Thus, if the libraries you need come with major parts of a proprietary operating system, the GPL says people can link your program with them without any conditions. The last FAQ is not very clear IMHO because the rule says "unless that component itself accompanies the executable" (as is the case with my distributed dll) but after the explanation says "the requirement to distribute source code for the whole program does not include those libraries, even if you distribute a linked executable containing them" Marco - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
