[Zlib-devel] zlib 1.2.4 released!

[John Bowler]

I've been running for a couple of days with William's zlib1.dll built from zlib 1.2.4.  Since I have a zlib1 built from 1.2.3 using Visual Studio Express 2010 (beta) I was able to hot swap that DLL for the 1.2.4 zlib1.

After I had done this the 'pngtest' program from libpng was linked to MSVCR100.dll *in addition* to all the things it had been linked to before, i.e. it was still also linked to msvcrt.dll.  This was a version of pngtest built on MinGW using the latest 1.5.0 beta of libpng.  Pngtest and libpng both use stdio and other C library functionality.

So I'd say that however it is built libz1.dll should not be linked to msvcr100.dll, or, indeed any other C runtime other than msvcrt.dll.

It's probably worth noting that pngtest doesn't use any of the zlib gzFile APIs, but I think it is safe to have multiple (FILE) implementations (i.e. multiple CRTs) in a single runtime just so long as you don't attempt to pass a (FILE*) from one to another.  The problem is the space issue - that the app ends up loading two different C runtimes.

John Bowler <jbowler at acm.org>