Re: [Mingw-users] using MinGW dlls in MSVC++ apps

[Roumen P. <bug...@ro...>]

Danny Smith wrote:

> Keith Marshall said"
>> Since mingwrt-3.14, IIRC, we have shipped import libs, and the 
>> corresponding oldname libs, to facilitate linking with MSVCR70, 
>> MSVCR71, MSVCR80 and MSVCR90, as alternatives to MSVCRT, (and we've 
>> also supported the debug variants of all of these).  The method of 
>> selecting from that list of alternatives, as described in the Wiki 
>> article, is simply the final piece of the jigsaw, to complete the 
>> infrastructure of that multiple runtime version support.
> 
> This whole msvcrt-versioning needs to be reviewsed  On my XP-sp2, the system MSVCRT.DLL
> (C:\windows\system32\msvcrt.dll)   contains *almost* all of the exports defined in mingw's
> msvcr71.def. Its internal version string is "7.0.2600.3085"  Perhaps, as with the w32api
> import libs, the default import lib should contain all the symbols supported by the most
> recent OS, leaving the onus of guarding against too-new imports/backward-compat issues to
> the header file guards  and the user's ability to avoid shooting self in foot.

MS C-runtime is not backward/forward compatible. Perhaps mingw rt has to 
include more import libraries as example libmsvcrt-xp.dll.a with import
symbols corresponding to 7.0 and LIBRARY msvcrt.dll.
What about mingwrt package to include predefined gcc specs files for
various MS C-runtime ?

> 
> Danny
> "A preposition is a word which you should not end a sentence with."

Roumen

P.S.: resent