Re: [bug-gnu-libiconv] libiconv 1.11.1 - MS VS 2005 and manifest files

[Bruno Haible]

Hello Milan,

> Microsoft CRT libraries are now available only through MS Redistributable 
> packages. MSDN has download site for these packages. These packages contain 
> CRT libraries, for different architectures, in different versions and 
> releases.
> ...
> What I tried to address in my previous posting wasn't how to make library 
> build with VS 2005 to run on machine that doesn't has required CRTs. I only 
> tried to address the question on how to resolve the situation with Manifest 
> files (more on this later).
> 
> This is what my intentions were: Build libiconv with VS 2005, thus making it 
> require VS 2005 CRT - MSVCR80.dll. Then, I'm assuming that deployment 
> machine has right version of MS Redistributable installed (it is standard 
> requirement of all VS 2005 applications).

Thanks for explaining. Sorry I had misunderstood the intention of your first
mail.

However, in this situation, and with this intent, your patch produces
executables (iconv.exe) which cannot be distributed without violating a
license.

There is probably no problem with distributing a built libiconv.dll this way:
the LGPL allows this, and you got to check your VS2005's EULA yourself.

But for programs that are under the GPL, such as iconv.exe of
libiconv 1.11.1, you are not allowed to distribute a binary that is linked
with a closed-source library that is not part of the normal installation of
the operating system. (Read the GPLv2. Read the GPLv3.) The MS
"Redistributables" are not part of the Windows OS to which they are
downloaded. 

You can certainly distribute the libiconv.dll that you built with your
patch. But I won't apply that patch because it too easily encourages people
to do things that are illegal.

Bruno