License Question

Hi,

I would like to ask a question that sure somebody else asked too, but I
can’t find a search option in the website of this mailing list.

In the faq licensing section, you say:
Q: Can I use SDL in a commercial application?
you’re fine.
You do not have to include the source code to your application, since
the end user can drop in a new version of the SDL shared library, which
is the intent of the license.

Full details are available at: http://www.libsdl.org/license.php

But from the full details I understand that I must make available the
OBJ code of my application, not just the EXE.

The application dynamically links to SDL, so you can replace it with
another version and it should work (I’ve just replaced the 1.2.5 with
the 1.2.7 SDL library with no problems), but you cannot touch the EXE as
it is compressed and encrypted.

So my question is, can I use the SDL in this case, provided I give
access to the SDL source code and lib, but only the EXE of my application?.

Thanks,
F?lix.A: The simple answer is “Yes”, just dynamically link with SDL and

if you dont compile SDL directly into the EXE and access it only as a library
(dll/so), you need not provide the source to your EXE file

if you make modifications to SDL but only include the modifications in the SDL
library (dll/so), you need to publish the source to those changes, but not to
the code that uses those changes through the library interface (like your
EXE)
-mikeOn Tuesday 06 July 2004 10:03 pm, F?lix wrote:

So my question is, can I use the SDL in this case, provided I give
access to the SDL source code and lib, but only the EXE of my application?.