[SDL] Embed SDL.dll in the .exe
Will Langford
unfies at gmail.com
Wed Sep 26 04:31:01 PDT 2007
> > Also, you do realize that releasing only statically linked executables
> > of a closed source application violates the licence of LGPL libs
> > (like SDL), right? You need to provide a dynamically linked version
> > as well, or linkable object files, or (obviously) the source code, or
> > otherwise ensure that users can use your software with whatever SDL
> > version they want.
>
> No surprise, I was pretty sure I'd get advice on why I don't want to
> do a static compilation - except I do want that :)
>
> The C game is GNU FreeDink, it is released under the GNU GPL:
> http://git.sv.gnu.org/gitweb/?p=freedink.git;a=summary
>
> I plan to provide several packages, statically compiled and
> dynamically compiled -- and people are still not happy they'll just
> ./configure && make && make install ;)
>
> Btw, static compilation of proprietary SDL apps does not break the
> LGPL if you provide the .o and every compilation tools needed by the
> user when he wants to use another version of SDL with your app. Using
> dynamic linking is the easiest way to comply with the LGPL, but not
> the only one!
David did point out that if you provided the object files and related
materials that you could still comply with LGPL.... so... ya skipped a bit
in his email :).
More to the point of my post -- I'm curious. If you statically link a GPL
program, doesn't the GPL license require what it's linked against to be GPL
as well ? I know the GPL is viral in many ways similar, but I'm uncertain
in this case... hence the need and rise of LGPL.
-Will
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20070926/81c4bddf/attachment.htm
More information about the SDL
mailing list