Re: [Gnuwin32-users] Re: Will the real libiconv please stand up! Was : Re: [Mingw-users] baby steps, an half-finshed packaging of libiconv (very boring)

[Kees Z. <kz...@us...>]

Gnuwin32 usually names the dll after the name of the package. So
for the libiconv package the dll is called libiconv.dll, and for
the barcode package the dll is called barcode.dll. But this usage is just
a matter of taste, not of principle, and it has not been always followed.

Kees Zeelenberg

----- Oorspronkelijk bericht -----
Van: "Bruno Haible" <br...@cl...>
Aan: "Tor Lillqvist" <tm...@ik...>
CC: "stefan" <st...@lk...>; <gnu...@li...>; <ko...@us...>; <dia...@gn...>;
<gim...@ya...>; <Min...@li...>
Verzonden: maandag 2 september 2002 21:37
Onderwerp: [Gnuwin32-users] Re: Will the real libiconv please stand up! Was : Re: [Mingw-users] baby steps, an half-finshed
packaging of libiconv (very boring)


> Tor Lillqvist 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)?
>
> Apparently so.
>
> I decided for the DLL name generated by Makefile.msvc - knowing that
> in the Woe32 world, the prefix "lib" is uncommon.
>
> The mingw32 porters of libtool decided to keep the "lib" prefix - for
> reasons I can only speculate about (maybe the desire to minimize the
> changes in Makefiles or in libtool?).
>
> Bruno
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> Gnuwin32-users mailing list
> Gnu...@li...
> https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
>