Win32: The binary pgsql package depends on MSVCR71.dll which we must not depend upon

[Phil Longstaff]

On October 3, 2009 09:58:14 am Christian Stimming wrote:
> Dear Phil,
>
> I've tracked down the bug below, which said some of the full win32 gnucash
> binary has a dependency on MSVCR71.DLL. That's the C runtime library of the
> rather old Microsoft Visual Studio compiler version 7.1 (Visual Studio
> 2003, I believe). Your pgsql binary package introduces this dependency into
> the gnucash win32 package.
>
> This kind of compiler-specific DLL cannot be expected to be present on the
> target system, so if it is really needed, one would have to include it in
> our binary package. However, in this case it rather means the binary DLLs
> for PgSQL which you collected from somewhere else have been compiled by
> that old visual studio compiler. Is this really necessary? Isn't there some
> way to get this without a dependency on the visual studio runtime?
>
> Oh, and there's a much more severe error, as mentioned by me in the
> bugzilla item: By including the suitable openssl DLLs (libeay32.dll,
> libssl32.dll, ssleay32.dll) in your pgsql binary, you're silently
> overwriting those openssl DLLs which we compile ourselves during the win32
> build, and on which the aqbanking library depends upon. In other words, the
> inclusion of the current pgsql binary package most probably will cause any
> SSL-related operation of aqbanking to crash badly.
>
> I propose to remove the pgsql part of the win32 binary for now, until we
> (resp. you) have found a better pgsql binary to include in our build.

That binary is the one which is directly available from the postgresql 
website.  Looks like I'll have to set up our own win32 build of postgresql.

Phil