Is the problematic section 6 in the LGPL you are refering to is
quote:
6. Revised Versions of the GNU Lesser General Public License.The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.
?
(this is from LGPL version 3.0)
If so, I fail to see how that is a problem. since:
quote:
The Simple DirectMedia Layer library is currently available under the GNU Lesser General Public License (LGPL) version 2.1 or newer.
means you can choose whichever version of the LGPL license that you'd like to follow (as long as it is of version 2.1 or higher)
Finally, according to the SDL website (http://www.libsdl.org/license-lgpl.php)
quote:
To comply with this license, you must give prominent notice that you use the Simple DirectMedia Layer library, and that it is included under the terms of the LGPL license. You must provide a copy of the LGPL license.
You must also do one of the following: 1. Link with the library as a shared object (e.g. SDL.dll or libSDL.so)
2. Provide the object or source code to your application along with any libraries and custom tools not available with a standard platform development kit. You may also simply provide a written offer, valid for three years, to provide these materials upon request to anyone with a legal copy of your application.
If you include the SDL library in binary form, you should also make available the source code to the version you provide, including any customizations you have made. If you link to a standard version of the library, simply referring to the SDL website is sufficient.
Also, I kind of stumbled upon this cool tutorial for SDL: http://cone3d.gamedev.net/cgi-bin/index.pl?page=tutorials/gfxsdl/index
Just in case someone is interested in it. (Or in case Toady still doesn't know SDL)
EDIT: Ahh, could the problem be if you need (for example) SDL1.2 and that will no longer be available on the SDL website at some distant point in the future? (which will mean using a newer version which could be under any license)
I highly doubt the chances of that happening. And even if it will, the dll will still most probably be available (if not on the SDL website, then somewhere else), so there would be no problems.
[ August 27, 2007: Message edited by: Slartibartfast ]