From: Earnie B. <ear...@ya...> - 2002-09-03 10:57:15
|
The libiconv name has already been standardized regardless of what OS it's on. You don't disagree with standardization do you? If I'm coming from a UNIX world looking for ported libraries, I'm most likely to search for libiconv instead of iconv. Earnie. Wu Yongwei wrote: > However, Win32 is NOT UNIX. I prefer to remove the lib- prefix. It is more > Win32-like (the UNIX style is not a reason on Win32). But I don't insist on > that. Some other projects (like expat) went to the other end to name the > MSVC DLL libxxxx.dll. The key point is that we should not have two names for > a DLL. > > Best regards, > > Wu Yongwei > > --- Original Message from Earnie Boyd --- > > Tor Lillqvist wrote: > > > Bruno Haible writes: > > > * If you want mingw32 binaries, go to http://mingwrep.sourceforge.net/ > > > > BTW, is it on purpose that these binaries use a different name for > > the DLL (libiconv.dll) than what you get if you compile with MSVC > > using the Makefile.msvc (iconv.dll)? > > The libiconv.dll is more standard with shared libraries from UNIX. I can > think of no other reason they would be different. > > Earnie. > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users |