Re: [msvcrt] how to handle msvcr*.dll ?

2005-11-28 Thread Daniel Remenak
On 11/27/05, Raphael [EMAIL PROTECTED] 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

Re: [msvcrt] how to handle msvcr*.dll ?

2005-11-28 Thread Raphael
On Monday 28 November 2005 19:46, Daniel Remenak wrote: On 11/27/05, Raphael [EMAIL PROTECTED] 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

Re: [msvcrt] how to handle msvcr*.dll ?

2005-11-28 Thread Uwe Bonnes
Raphael == Raphael [EMAIL PROTECTED] writes: Raphael On Monday 28 November 2005 19:46, Daniel Remenak wrote: snip. Windows does not and will not distribute them, and neither should wine. What about winelib on non-X86? Raphael I know that but many application expect

Re: [msvcrt] how to handle msvcr*.dll ?

2005-11-28 Thread Robert Shearman
Uwe Bonnes wrote: Raphael == Raphael [EMAIL PROTECTED] writes: Raphael On Monday 28 November 2005 19:46, Daniel Remenak wrote: snip. Windows does not and will not distribute them, and neither should wine. What about winelib on non-X86? msvcr*.dll =

[msvcrt] how to handle msvcr*.dll ?

2005-11-27 Thread Raphael
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