SDL-1-2-11 MSVS 2005 SDL DLL Entry Error

Good Afternoon,

I’m rebuilding an application that once worked on a 2000 & MSVC 6 environment -
alias that system died. The replacement is a XP Pro - MSVS 2005 (V8)
environment. I’m running into the following error when I run the program:

“The procedure entryp point SDL_strlcpy could not be located in the dynamic
link library SDL.dll”.

I’ve tried the precompiled libraries/DLL and compiled the SDL environment,
using the MSVC guides, and received the same result.

I remember seeing something about this issue and a resolution, however, I
haven’t been able to find the thread. I assume its something basic and related
to the change in my environment.

Thanks for any assistance in advance,

Keith:)

Hello Keith,

Friday, October 6, 2006, 9:41:30 PM, you wrote:

Good Afternoon,

I’m rebuilding an application that once worked on a 2000 & MSVC 6 environment -
alias that system died. The replacement is a XP Pro - MSVS 2005 (V8)
environment. I’m running into the following error when I run the program:

“The procedure entryp point SDL_strlcpy could not be located in the dynamic
link library SDL.dll”.

I’ve tried the precompiled libraries/DLL and compiled the SDL environment,
using the MSVC guides, and received the same result.

I remember seeing something about this issue and a resolution, however, I
haven’t been able to find the thread. I assume its something basic and related
to the change in my environment.

Thanks for any assistance in advance,

Everything should be fine if you are using SDL.dll and SDLmain.lib
compiled with MSVC 2005. I am using that setup and it works correctly.–
Best regards,
Peter mailto:@Peter_Mulholland

I’m guessing here but I’d say that the program is finding another copy
of SDL.DLL other than the one you think it’s finding. I found a SDL.DLL
that I didn’t install explicitly in several directories on my system. I
suspect they were placed there when I installed a game or some other
graphic oriented program.

Lilith

Good Afternoon,

I’m rebuilding an application that once worked on a 2000 & MSVC 6
environment

alias that system died. The replacement is a XP Pro - MSVS 2005 (V8)

environment. I’m running into the following error when I run the
program:

“The procedure entryp point SDL_strlcpy could not be located in the
dynamic
link library SDL.dll”.

I’ve tried the precompiled libraries/DLL and compiled the SDL
environment,
using the MSVC guides, and received the same result.

I remember seeing something about this issue and a resolution,
however, I
haven’t been able to find the thread. I assume its something basic
and>>> On 10/6/2006 at 3:41 PM, in message <loom.20061006T223146-703 at post.gmane.org>, Keith <k.mahnken at ameritech.net> wrote:
related
to the change in my environment.

Thanks for any assistance in advance,

Keith:)


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

Lilith Calbridge <lilith dcccd.edu> writes:

I’m guessing here but I’d say that the program is finding another copy
of SDL.DLL other than the one you think it’s finding. I found a SDL.DLL
that I didn’t install explicitly in several directories on my system. I
suspect they were placed there when I installed a game or some other
graphic oriented program.

Lilith

Thanks for the quick assistance and Lilith was correct in that multiple
copies
of SDL were available.

I deleted them, rebuilt and then of course it could find the DLLs. Yep, forgot
to make sure the build process include the correct SDL library to copy the DLLs
from. Things are working just fine from an SDL perspective of course I know
have correct the issue with the program.

Thanks for the quick assistance! Have a great weekend!

Keith:)

Hello Keith,

Friday, October 6, 2006, 10:23:56 PM, you wrote:

Thanks for the quick assistance and Lilith was correct in that multiple
copies of SDL were available.

I deleted them, rebuilt and then of course it could find the DLLs. Yep, forgot
to make sure the build process include the correct SDL library to copy the DLLs
from. Things are working just fine from an SDL perspective of course I know
have correct the issue with the program.

Didn’t catch Lilith’s reply yet, but that was a good call :slight_smile:

It’s worth checking out your exe with Depends to catch this kind of
thing, too.

Programs absolutely should NOT be installing SDL.dll into global
search path places, ie the Windows directory - ALWAYS in the program’s
own directory. Same for any of the SDL extra dll’s.

It’s rather unfortunate though that Microsoft seem to have made MSVC
2005 produced code rather intolerant of the old msvcrt.dll runtime. I
believe the prebuilt SDL binaries use this because they are built with
cygwin/mingw which uses this runtime.–
Best regards,
Peter mailto:@Peter_Mulholland