SDL2 and library naming conventions

SDL Development
1

I’m using SDL2 now and I’m wondering, should I name things like:

SDL2.DLL
SDL2_image.DLL
SDL2_ttf.DLL
SDL2_sound.DLL
et cetera,

or should I name things like
SDL.DLL
SDL_image.DLL
SDL_ttf.DLL
SDL_sound.DLL
?

I currently have a mix and that seems like I’m being inconsistent. Is there any good reason to do it one way or the other, and which way do you folks think is the preferred way?

2

On windows it really doesn’t matter because typically the SDL shared
libraries will be in the same directory as the binary, however, in nix,
the naming convention is now SDL2_ - it may be good to keep to that.On Tue, Sep 25, 2012 at 11:06 AM, Trev wrote:

**
I’m using SDL2 now and I’m wondering, should I name things like:

SDL2.DLL
SDL2_image.DLL
SDL2_ttf.DLL
SDL2_sound.DLL
et cetera,

or should I name things like
SDL.DLL
SDL_image.DLL
SDL_ttf.DLL
SDL_sound.DLL
?

I currently have a mix and that seems like I’m being inconsistent. Is
there any good reason to do it one way or the other, and which way do you
folks think is the preferred way?

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

3

Ok, I guess I’ll consistently rename according to the SDL2_* convention.

I’ve been trying to do this and I keep getting annoying errors about missing an “SDL.dll” file when I call a SDL2_sound function. I swear there isn’t a single reference SDL.dll or SDL.lib and everything references only SDL2.dll and SDL.lib, but I suppose there must be a reference to it somewhere. I guess I’ll just have to keep looking and carefully rebuild everything from scratch.

4

Yeah, you’ll need to rebuild SDL with that naming convention.On Tue, Sep 25, 2012 at 12:40 PM, Trev wrote:

**
Ok, I guess I’ll consistently rename according to the SDL2_* convention.

I’ve been trying to do this and I keep getting annoying errors about
missing an “SDL.dll” file when I call a SDL2_sound function. I swear there
isn’t a single reference SDL.dll or SDL.lib and everything references only
SDL2.dll and SDL.lib, but I suppose there must be a reference to it
somewhere. I guess I’ll just have to keep looking and carefully rebuild
everything from scratch.

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

5

SDL2, SDL2_image, and SDL2_ttf all work fine with a consistent SDL2_* naming scheme, but SDL2_sound seems to always ask for a “SDL.dll”. I wonder if some versions of SDL_sound have some sort of explicit reference to “SDL.dll”. To make matters works, there are multiple versions of SDL_sound and I’m not sure which version I should use. Perhaps I should just use the older named scheme (without the “2”). At least that the requested “SDL.dll” file will be there.

I really do hate linking related bugs. :x

6

Have you tried to spot the linking issues with a dependency tool like
depends?

http://www.dependencywalker.com/

Another issue might be that one of those libraries is loading directly the
ones you’re having problems with.–
Paulo

On Tue, Sep 25, 2012 at 9:33 PM, Trev wrote:

**
SDL2, SDL2_image, and SDL2_ttf all work fine with a consistent SDL2_*
naming scheme, but SDL2_sound seems to always ask for a “SDL.dll”. I wonder
if some versions of SDL_sound have some sort of explicit reference to
"SDL.dll". To make matters works, there are multiple versions of SDL_sound
and I’m not sure which version I should use. Perhaps I should just use the
older named scheme (without the “2”). At least that the requested "SDL.dll"
file will be there.

I really do hate linking related bugs. [image: Mad]

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

7

Hello !

I’m using SDL2 now and I’m wondering, should I name things like:

SDL2.DLL
SDL2_image.DLL
SDL2_ttf.DLL
SDL2_sound.DLL
et cetera,

or should I name things like
SDL.DLL
SDL_image.DLL
SDL_ttf.DLL
SDL_sound.DLL
?

I currently have a mix and that seems like I’m being inconsistent.
Is there any good reason to do it one way or the other, and
which way do you folks think is the preferred way?

I would choose way number one using SDL2.dll, SDL2_image.dll, …,
even if it does not matter for the programm itself, a user that
might want to replace your SDL(2).dll,…, with his own DLLs,
knows instant what SDL version 1 or 2 your programm uses.

CU