Manish,

On Win32, libiconv can be built either as a DLL (with associated import
library) or as a "static" library. The zip file includes the results of
both builds: iconv.lib is the import library for iconv.dll; iconv_a.lib
is the static library. The iconv_a.lib file is what you get when you use
the standard build procedure without the "DLL=1" option. The result
library was renamed to iconv_a.lib to prevent the problems arising from
having two different files names "iconv.lib".

At least I think that's how it happened. Am I right, Igor?

Eric Zurcher
CSIRO Plant Industry
Canberra, Australia
[EMAIL PROTECTED] 


-----Original Message-----
Date: Tue, 28 Feb 2006 16:40:20 -0800
From: Manish Marathe <[EMAIL PROTECTED]>
Subject: [xml] win32 file support for building libxml
To: XML Group <xml@gnome.org>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=iso-8859-1

Hello All,

I found a link ftp://xmlsoft.org/win32/ which has FTP down-loadable
win32 files for libxml and libxslt. One of those is
iconv-1.9.1.win32.zip which has pre-built libiconv 1.9.1 libraries. 

I could build libiconv except iconv_a.lib. I was just curious whether
anyone here built that library because in the standard build procedure
of libiconv on Win32 iconv_a.lib does not get created.

Thanks for your help.

-Manish
_______________________________________________
xml mailing list, project page  http://xmlsoft.org/
xml@gnome.org
http://mail.gnome.org/mailman/listinfo/xml

Reply via email to