The official VC++ SDL DLLs seem to be linked against libcmt.lib
instead of msvcrt.dll. Is there any specific reason for this ?
Markus
---- Markus F.X.J. Oberhumer <@Markus_F.X.J_Oberhum> ----
---- http://wildsau.idv.uni-linz.ac.at/mfx/ ----
---- 5E CB 5C 85 DE AF 9E BF E9 DA 7E 6A 39 F8 CC 67 ----
3 WARPS TO URANUS
The official VC++ SDL DLLs seem to be linked against libcmt.lib
instead of msvcrt.dll. Is there any specific reason for this ?
Nope.
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
I just wondered if this has any impacts on memory managment, file
handles, etc (note that SDL currently has a privte copy of all C
library functions like malloc). I’m working on embedding SDL in Python
via a dynamic extension module, and both python15.dll, tcl80.dll and
tk80.dll are linked against msvcrt.dll.
Wouldn’t this be the right thing for the VC SDL as well - I’d guess
the mingw version alread is.
Markus
---- Markus F.X.J. Oberhumer <@Markus_F.X.J_Oberhum> ----
---- http://wildsau.idv.uni-linz.ac.at/mfx/ ----
---- 5E CB 5C 85 DE AF 9E BF E9 DA 7E 6A 39 F8 CC 67 ----
3 WARPS TO URANUSOn 25-Jan-2000 Sam Lantinga wrote:
The official VC++ SDL DLLs seem to be linked against libcmt.lib
instead of msvcrt.dll. Is there any specific reason for this ?
Nope.
I think you’re right. Can you send me the changes necessary for this?
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software> On 25-Jan-2000 Sam Lantinga wrote:
The official VC++ SDL DLLs seem to be linked against libcmt.lib
instead of msvcrt.dll. Is there any specific reason for this ?
Nope.
I just wondered if this has any impacts on memory managment, file
handles, etc (note that SDL currently has a privte copy of all C
library functions like malloc). I’m working on embedding SDL in Python
via a dynamic extension module, and both python15.dll, tcl80.dll and
tk80.dll are linked against msvcrt.dll.
Wouldn’t this be the right thing for the VC SDL as well - I’d guess
the mingw version alread is.
–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
Just use the switch “/MD” instead of “/MT” in your project file
settings.
Markus
---- Markus F.X.J. Oberhumer <@Markus_F.X.J_Oberhum> ----
---- http://wildsau.idv.uni-linz.ac.at/mfx/ ----
---- 5E CB 5C 85 DE AF 9E BF E9 DA 7E 6A 39 F8 CC 67 ----
3 WARPS TO URANUSOn 26-Jan-2000 Sam Lantinga wrote:
I just wondered if this has any impacts on memory managment, file
handles, etc (note that SDL currently has a privte copy of all C
library functions like malloc). I’m working on embedding SDL in Python
via a dynamic extension module, and both python15.dll, tcl80.dll and
tk80.dll are linked against msvcrt.dll.
Wouldn’t this be the right thing for the VC SDL as well - I’d guess
the mingw version alread is.
I think you’re right. Can you send me the changes necessary for this?
I’ve just compiled SDL 1.0.3 under Visual C++ 6 and it’s even worse
than I thought - SDL seems to be linked against the (default) single
threaded LIBC !
Please change the project file settings under C/C++ - Code Generation -
Runtime Library to “Multithreaded DLL” (this should result in a
compiler option “/MD”). I consider this a serious problem.
Markus
---- Markus F.X.J. Oberhumer <@Markus_F.X.J_Oberhum> ----
---- http://wildsau.idv.uni-linz.ac.at/mfx/ ----
---- 5E CB 5C 85 DE AF 9E BF E9 DA 7E 6A 39 F8 CC 67 ----
3 WARPS TO URANUSOn 26-Jan-2000 Sam Lantinga wrote:
On 25-Jan-2000 Sam Lantinga wrote:
The official VC++ SDL DLLs seem to be linked against libcmt.lib
instead of msvcrt.dll. Is there any specific reason for this ?
Nope.
I just wondered if this has any impacts on memory managment, file
handles, etc (note that SDL currently has a privte copy of all C
library functions like malloc). I’m working on embedding SDL in Python
via a dynamic extension module, and both python15.dll, tcl80.dll and
tk80.dll are linked against msvcrt.dll.
Wouldn’t this be the right thing for the VC SDL as well - I’d guess
the mingw version alread is.
I think you’re right. Can you send me the changes necessary for this?
I’ve just compiled SDL 1.0.3 under Visual C++ 6 and it’s even worse
than I thought - SDL seems to be linked against the (default) single
threaded LIBC !
Please change the project file settings under C/C++ - Code Generation -
Runtime Library to “Multithreaded DLL” (this should result in a
compiler option “/MD”). I consider this a serious problem.
I have in the latest CVS version. The next release will be linked
against MSVCRT.DLL.
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec