Re: Re[2]: [Mingw-users] missing ISO C89/C99 functions in runtime

[<dan...@ya...>]

--- SONE Takeshi <ts...@cm...> wrote: > On Tue, Dec 05, 2000 at
12:33:15PM -0800, Earnie Boyd wrote:
> > --- Paul Sokolovsky <pa...@is...> wrote:

> I assume you are to create a new _import_ library for MSVCP60.DLL,
> because
> of the name 'libnewname.a'.
> This will cause another runtime problem, which is worse than
> MSVCRT/CRTDLL
> issue, because MSVCP60.DLL is more likely to change, and does not
> come
> with most versions of Windows (I think WinMe is the only one with
> MSVCP60.DLL builtin).
> I'd name it 'libmsvcp60.a' in this case, and not put it in specs,
> so that user is notified that the program requires special runtime
> DLL.

Forget about MSVCP60.dll.  It's a C++ dll with only a few usable (to
mingw) symbols.  Hmm?  Why are libc symbols there anyway?

> 
> If you create a new _static_ library from PD source, the name
> 'libnewname.a' is confusing.  It better simply go into libmingw32.a.
> 

Why?  If we do it right libnewname.a should be usuable by other Win32
compilers (eg ICC) as well as mingw.  IMHO libmingw.a should remain
specific to mingw. 


Danny

> -- 
> Takeshi
> _______________________________________________
> MinGW-users mailing list
> Min...@li...
> 
> You may change your MinGW Account Options at:
> http://lists.sourceforge.net/mailman/listinfo/mingw-users


_____________________________________________________________________________
http://clubs.yahoo.com.au - Yahoo! Clubs
- Join a club or build your own!