[Zlib-devel] 1.2.5 DLL broken?

[jbowler at acm.org]

From: zlib-devel-bounces at madler.net [mailto:zlib-devel-bounces at madler.net] On Behalf Of Mark Adler
>On Jun 19, 2011, at 1:11 PM, <jbowler at acm.org> <jbowler at acm.org> wrote:
>> My solution for libpng was to make a libpng DLL that statically links (and does not export)
>>the relevant zlib modules.  I do this for Visual Studio and OpenWatcom.
>
>Should this be in the DLL_FAQ?

Probably not, because it just works to copy the Zlib source files into a new Visual Studio (or OpenWatcom) DLL project and do it yourself.  That's because the settings on the new project match those on the rest of the application so there is no confusion.

The most important thing in the DLL_FAQ is to emphasis that a home grown DLL must be given a unique name; never ZLIB1.DLL and preferably not ZLIB.DLL.

Libpng has historically offered a set of makefiles for every compiler under the sun and that is where the problem starts; the libpng makefiles (and projects) have one set of compile/link settings that never quite match those used elsewhere.

John Bowler <jbowler at acm.org>