<snip> >> Is static linking of these a bad idea, for any licensing reasons? (I'm >> fairly clueless about these things...) > Static linking GPL libraries into a closed source executable is not allowed. > > Static linking LGPL libraries into a closed source executable is allowed > but I believe that the means to relink the executable must be provided > somewhere. In practice that means making the object code of the closed > source parts available. Relevant T&C:
http://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic > > The above LGPL case should be the situation with kvasd, I can't answer > for sure since I don't know which libraries are being statically linked. > > The complexity of making object code available might be not worth the > trouble and dynamic linking may be easiest IMHO. AFAIK dynamic linking > is the way that this is done in almost all proprietary products. >> -- Joe, K1JT 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
