On 11/27/05, Raphael <fenix(a)club-internet.fr> wrote:
Hi,
since visual studio .net (2002,3,5) MS provides newer versions of msvcrt: - msvcr70.dll - msvcr71.dll - msvcr80.dll ... (and same equivalents for msvcp*.dll)
how we will handle that on wine: - creating new dll forlders and using forwards to current msvcrt.dll or - creating only new .spec files on msvcrt folder ?
Regards, Raphael
See: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/... Particularly the section "What is the difference between msvcrt.dll and msvcr71.dll?" Copied here in case the URL changes: "The msvcrt.dll is now a "known DLL," meaning that it is a system component owned and built by Windows. It is intended for future use only by system-level components. An application should use and redistribute msvcr71.dll, and it should avoid placing a copy or using an existing copy of msvcr71.dll in the system directory." msvcr## and msvcp## are not system dlls, they're application dlls. msvcrt.dll *is* a system dll. It wouldn't make sense for us to create msvcr##/msvcp##, since they are supposed to be distributed by the application and not even placed in the system directory. Windows does not and will not distribute them, and neither should wine. --Daniel Remenak