On Thu, 2007-11-15 at 11:05 -0800, Chris Albertson wrote: > In your case where you are wrinting code and you make use of GPL'd > code then yes you should release your code under GPL. But there is > an exception. The exception is for a GPL'd component that provides > some well defined functon that could be provided by some other > component. An example of this would by a Windows DLL. Just because > your program calls a DLL that is GPLd your program does not have to > be GPL'd. The key is the degree of separation. The DLL case is clear > cut because any number of programs can call the same DLL and the > DLL can be distributed independently of the programs that use it. > As long as you maintain this level of independence you are not > effected by GPL.
LGPL code is the exception.. if a DLL is GPL and you dynamically link against it, your program must be GPL. No exceptions unless the author of the DLL granted it. > If you link in the GPL'd code and make a single object that cannot > be taken apart then the object you made must be covered by GPL > and you need to offer the source code. If you link in GPL'd code, period. That includes dynamic linking, and any attempts to "wrap" the proprietary code in a GPL'd wrapper. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user