From: Danny Smith <dannysmith@cl...> - 2008-04-21 04:58:46
Monday, 21 April 2008 8:41 a.m.
> Danny Smith wrote:
> > On newer versions of windows, the system MSVCRT.DLL does
> contain the new functionality of
> > at least msvcr71.dll
> > Foe example, on XP C:\WINDOWS\SYTEM32\MSVCRT.DLL is
> version 7.0.2600.2180 and at first
> > glance is equivalent to mscvr71.dll
> Interesting; I didn't know that. However, to take advantage of that,
> you'd need a different import library than any of the ones
> provided by
> the mingw project: because you need the import symbols from
> -- but our msvcrt71.a import library hardcodes the dll name
> as msvcrt71.dll.
> Of course, once you created your special import library (msvcrt71
> imports, but msvcrt.dll embedded dll name), your app would then only
> work on Windows XP and above. Running your app on NT/2k
> would result in
> a 0xC0000135 (STATUS_DLL_NOT_FOUND) runtime error and an 'Application
> Failed To Initialize Properly' dialog.
AS long as the headers are quarded with appropriate #if __MSVC_VERSION > XXX, and the
default remains 0x0600, there should be no "you-broke-it" surprises with a libmsvcrt.a
that contains all the mscvrt names on, say Vista. Thats how the the win32api libs
operate (and the way the PSDK works too for that matter). The libmsvcr70.a and co were
probably not a good idea.
Get latest updates about Open Source Projects, Conferences and News.