apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mladen Turk <mt...@apache.org>
Subject Re: svn commit: r434327 - in /apr/apr/trunk: CHANGES include/arch/win32/apr_arch_threadproc.h misc/win32/start.c threadproc/win32/threadpriv.c
Date Fri, 15 Sep 2006 18:00:14 GMT
Greg Marr wrote:
> At 12:59 PM 9/15/2006, Mladen Turk wrote:
>> Greg Marr wrote:
>>> At 12:06 PM 9/15/2006, William A. Rowe, Jr. wrote:
>>>> Quick observation, but MSVCRTD.lib in combination with VS 2005?
>>> Yes, the lib file does not have the version number in the filename.
>> ???
>> What are you talking about?
> The DLL for VS 2003 is MSVCRT71d.dll, but the lib file is MSVCRTd.lib.
> The DLL for VS 2005 is MSVCRT80d.dll, but the lib file is MSVCRTd.lib.
> This way, the user doesn't have to change their project settings or 
> pragmas when moving from one version to the next.

Right. So what?
Still don't get how is that related to the problem?
Since I use VS2005, the final exe will be linked with
MSVCRT80*.dll. The same is in place on Win32/x86
(same code, same compiler).
Is it so hard to understand that the same code,
with the same compiler on WIN64/x64 does not work,
while it works on WIN32/x86?

VC6/x86 lib,dll works
VS2005/x86 lib,dll works
VS2005/x64 creates the linker warnings I noted, and it doesn't work.


View raw message