Quick question regarding distribution

Hi all,

I am new to SDL, so please forgive me if this question has been addressed
before. First of all I want to extend my thanks to the developers for what
seems to be a simple, easy to use yet very sophisticated library! Now, to my
actual question.

In the source snapshot zip archive, I see a file called README-SDL.txt. This
file says:

“Please distribute this file with the SDL runtime environment:”

Does this mean that I have to redistribute this file with any binary
packages that I release which links statically to SDL? I would rather not do
so if it is not an official requirement, which the Zlib/Libpng license does
not seem to indicate that it is.

Thanks in advance for any clarifications on this.

Kind regards,

Philip Bennefall

Nope, it’s not required, although some attribution is appreciated. :slight_smile:

Cheers!On Wed, Aug 7, 2013 at 1:21 PM, Philip Bennefall wrote:

Hi all,

I am new to SDL, so please forgive me if this question has been addressed
before. First of all I want to extend my thanks to the developers for what
seems to be a simple, easy to use yet very sophisticated library! Now, to
my actual question.

In the source snapshot zip archive, I see a file called README-SDL.txt.
This file says:

“Please distribute this file with the SDL runtime environment:”

Does this mean that I have to redistribute this file with any binary
packages that I release which links statically to SDL? I would rather not
do so if it is not an official requirement, which the Zlib/Libpng license
does not seem to indicate that it is.

Thanks in advance for any clarifications on this.

Kind regards,

Philip Bennefall
_____________**
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/**listinfo.cgi/sdl-libsdl.orghttp://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Thanks, Sam. I just wanted to make sure.

On a different note, if I want to compile SDL into a static library, should I #define any macros in order to make it not export its symbols like it would for a dll?

Kind regards,

Philip Bennefall----- Original Message -----
From: Sam Lantinga
To: @Philip_Bennefall ; SDL Development List
Sent: Thursday, August 08, 2013 8:18 AM
Subject: Re: [SDL] Quick question regarding distribution

Nope, it’s not required, although some attribution is appreciated. :slight_smile:

Cheers!

On Wed, Aug 7, 2013 at 1:21 PM, Philip Bennefall <@Philip_Bennefall> wrote:

Hi all,

I am new to SDL, so please forgive me if this question has been addressed before. First of all I want to extend my thanks to the developers for what seems to be a simple, easy to use yet very sophisticated library! Now, to my actual question.

In the source snapshot zip archive, I see a file called README-SDL.txt. This file says:

"Please distribute this file with the SDL runtime environment:"

Does this mean that I have to redistribute this file with any binary packages that I release which links statically to SDL? I would rather not do so if it is not an official requirement, which the Zlib/Libpng license does not seem to indicate that it is.

Thanks in advance for any clarifications on this.

Kind regards,

Philip Bennefall 
_______________________________________________
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Philip Bennefall wrote:

On a different note, if I want to compile SDL into a static library, should
I #define any macros in order to make it not export its symbols like it
would for a dll?

You don’t have to hide them. It may be advantageous later when someone
tries to access your application in different ways. On Windows, code
has to specifically ask for the the exported symbols of the executable
so I don’t think there will be any conflicts. This may be different
for the other platforms.

If you really don’t want to export the symbols on Windows, define
DECLSPEC="" when building SDL.

I don’t know if this is already handled with the autotools script, but
it would be something like
DECLSPEC=attribute((visibility(“hidden”))) for gcc.

Hi there,

I actually ended up defining DECLSPEC="" last night, as I looked a bit
inside the SDL source and saw that that is the macro that it uses.

Thanks for the tip!

Kind regards,

Philip Bennefall> ----- Original Message -----

From: norfanin@gmail.com (Norfanin)
To: “SDL Development List”
Sent: Friday, August 09, 2013 12:37 PM
Subject: Re: [SDL] Quick question regarding distribution

Philip Bennefall wrote:

On a different note, if I want to compile SDL into a static library,
should
I #define any macros in order to make it not export its symbols like it
would for a dll?

You don’t have to hide them. It may be advantageous later when someone
tries to access your application in different ways. On Windows, code
has to specifically ask for the the exported symbols of the executable
so I don’t think there will be any conflicts. This may be different
for the other platforms.

If you really don’t want to export the symbols on Windows, define
DECLSPEC="" when building SDL.

I don’t know if this is already handled with the autotools script, but
it would be something like
DECLSPEC=attribute((visibility(“hidden”))) for gcc.


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org