1
Building instructions for the DLL versions of Zlib 1.2.4
2
========================================================
4
This directory contains projects that build zlib and minizip using
5
Microsoft Visual C++ 9.0/10.0, and Visual C++ .
7
You don't need to build these projects yourself. You can download the
9
http://www.winimage.com/zLibDll
11
More information can be found at this site.
13
first compile assembly code by running
14
bld_ml64.bat in contrib\masmx64
15
bld_ml32.bat in contrib\masmx86
20
Build instructions for Visual Studio 2008 (32 bits or 64 bits)
21
--------------------------------------------------------------
22
- Uncompress current zlib, including all contrib/* files
23
- Open contrib\vstudio\vc9\zlibvc.sln with Microsoft Visual C++ 2008.0
24
- Or run: vcbuild /rebuild contrib\vstudio\vc9\zlibvc.sln "Release|Win32"
26
Build instructions for Visual Studio 2010 (32 bits or 64 bits)
27
--------------------------------------------------------------
28
- Uncompress current zlib, including all contrib/* files
29
- Open contrib\vstudio\vc10\zlibvc.sln with Microsoft Visual C++ 2010.0
34
- To use zlibwapi.dll in your application, you must define the
35
macro ZLIB_WINAPI when compiling your application's source files.
40
- This DLL, named zlibwapi.dll, is compatible to the old zlib.dll built
41
by Gilles Vollant from the zlib 1.1.x sources, and distributed at
42
http://www.winimage.com/zLibDll
43
It uses the WINAPI calling convention for the exported functions, and
44
includes the minizip functionality. If your application needs that
45
particular build of zlib.dll, you can rename zlibwapi.dll to zlib.dll.
47
- The new DLL was renamed because there exist several incompatible
48
versions of zlib.dll on the Internet.
50
- There is also an official DLL build of zlib, named zlib1.dll. This one
51
is exporting the functions using the CDECL convention. See the file
52
win32\DLL_FAQ.txt found in this zlib distribution.
54
- There used to be a ZLIB_DLL macro in zlib 1.1.x, but now this symbol
55
has a slightly different effect. To avoid compatibility problems, do