Re: [bug-gnu-libiconv] libiconv question

[Bruno Haible]

Hello,

> This letter I use Google to translate, if not understand, I say sorry.

It is good that you tell that this is machine-translated English.
Otherwise I would have thought that are an English speaker with poor
education.

> Hello there! Officials, I'm a Chinese, read your library documents, I am very 
> uncomfortable, why not compile the libiconv environment in the Microsoft 
> environment? Do not you support Microsoft? Okay, I'm sorry. I through the 
> network query to the Microsoft environment compiler method. But your libiconv 
> library can only support 32-bit program, why? Why not support 64-bit program, 
> is the current 64-bit program is not popular? Of course, you will say that I 
> use 64-bit procedures to call Dll not on the line? I use your source code 
> compiled into 64-bit not on the line? But you do so, will lead to memory 
> leaks! We all know the difference between 32-bit and 64-bit pointers, one is 
> 4 bytes, an 8 bytes, are not compatible with each other! Or size_t this type 
> in 64-bit will become __int64, you know do not know ah?

I think that all your questions are answered by the README.windows file
from the source distribution [1].

> If you can receive this message, I hope you can give an explanation in the 
> official website, or in the official website to write the windows method.

In GNU, build instructions are usually found in the top-level files of the
source distribution of a package, not in the official documentation / manual.

Bruno

[1] 
http://git.savannah.gnu.org/gitweb/?p=libiconv.git;a=blob_plain;f=README.windows;hb=HEAD