[SDL] License Issues
Anoq of the Sun
anoq at HardcoreProcessing.com
Thu Mar 22 13:39:53 PST 2001
Joe Tennies wrote:
> I have noticed this and been wondering about it for some time now.
> SDLmain.lib is a statically linked library (for Borland's Compiler the
> SDL_main.c must be compiled into the project), yet it is under the LGPL
> license. By the license, we must be able to either a) recompile the program
> if a change occurred to the library or b) have it dynamically linked so only
> the libray needs to be changed. If I am not mistaken, this means that any
> project that uses the SDL_main.lib must be open-sourced.
> I think that this goes against the very concept of the SDL. I know one
> could just go and make a WinMain and a main and whatever else, but that just
> seems a little odd to me. I think that this should either be a) made more
> clear on the web page and documentation or b) remove the particular file
> from the LGPL license (I believe you can still require them to dynamically
> link to the SDL to use SDLmain.lib).
Sam Lantinga wrote:
> This is why, if you look at the source for SDL_main.c, you'll find that
> the source code has been placed in the public domain.
> You're perfectly fine linking SDL_main.c (and libraries consisting of it)
> with closed-source programs, with no license restrictions whatsoever.
FYI - I have also written a library which will handle the
WinMain problem. It is heavily inspired by SDL, but it is
The only "license" for it is:
"There is no warranty of any kind and I will not be
held responsible for any problems it may cause.
Use at your own risk!" :)
Maybe somebody will find it useful :)
More information about the SDL