Just for the record (and FYI), a Windows app built against SDL.dll v1.2.10
libs will not run with previous versions of SDL.dll. It will not be loaded
because of forced dependencies on SDL_strlcpy function et al in SDLmain lib.
This is, of course, not the same as a dependency on a newly added symbol
that a coder consciously decides to use and cut off the backward
compatibility at that point.
To remedy this, you can build your SDL.dll-using Windows apps against SDL
1.2.9 libs and still ship SDL.dll 1.2.10 with your binaries with no ill
effects.
-Alex.
Hello Alex,
Tuesday, May 30, 2006, 9:37:07 PM, you wrote:
AV> Just for the record (and FYI), a Windows app built against SDL.dll v1.2.10
AV> libs will not run with previous versions of SDL.dll. It will not be loaded
AV> because of forced dependencies on SDL_strlcpy function et al in SDLmain lib.
AV> This is, of course, not the same as a dependency on a newly added symbol
AV> that a coder consciously decides to use and cut off the backward
AV> compatibility at that point.
AV> To remedy this, you can build your SDL.dll-using Windows apps against SDL
AV> 1.2.9 libs and still ship SDL.dll 1.2.10 with your binaries with no ill
AV> effects.
This is generally not a problem as it is a Bad Idea to globally
install SDL anyway (ie into system32). Much better to install SDL into
your program’s dir.–
Best regards,
Peter mailto:@Peter_Mulholland