Lines Matching +full:readme +full:. +full:installer
2 Frequently Asked Questions about ZLIB1.DLL
6 of the common DLL build of zlib, named ZLIB1.DLL. If you have
9 http://www.gzip.org/zlib/zlib_faq.html
12 1. What is ZLIB1.DLL, and how can I get it?
14 - ZLIB1.DLL is the common build of zlib as a DLL.
15 (Please remark the character '1' in the name.)
17 Applications that link to ZLIB1.DLL can rely on the following
21 files "zlib.h" and "zlib.def", found in an official zlib
22 source distribution.
23 * The symbols are exported by name, not by ordinal.
24 * The exported names are undecorated.
25 * The calling convention of functions is "C" (CDECL).
26 * The ZLIB1.DLL binary is linked to MSVCRT.DLL.
28 The archive in which ZLIB1.DLL is bundled contains compiled
29 test programs that must run with a valid build of ZLIB1.DLL.
33 and build settings. If you do build the DLL yourself, please
36 the original ZLIB1.DLL distribution.
39 please use a different file name.
42 2. Why did you change the name of the DLL to ZLIB1.DLL?
43 What happened to the old ZLIB.DLL?
45 - The old ZLIB.DLL, built from zlib-1.1.4 or earlier, required
47 a static build. The DLL settings were supposed to be enabled
48 by defining the macro ZLIB_DLL, before including "zlib.h".
52 * ZLIB_DLL was missing from the old makefile. When building
53 the DLL, not all people added it to the build options. In
54 consequence, incompatible incarnations of ZLIB.DLL started
55 to circulate around the net.
60 functions. Failure to do so resulted in creating binaries
61 that were unable to run with the official ZLIB.DLL build.
66 the new DLL under a different name.
68 We chose the name ZLIB1.DLL, where '1' indicates the major
69 zlib version number. We hope that we will not have to break
71 zlib-1.x series will last.
75 longer dependents on it.
78 3. Can I build ZLIB.DLL from the new zlib sources, and replace
79 an old ZLIB.DLL, that was built from zlib-1.1.4 or earlier?
82 keywords to the macros ZEXPORT and ZEXPORTVA. In practice,
83 it depends on what you mean by "an old ZLIB.DLL", because the
84 old DLL exists in several mutually-incompatible versions.
86 being used in your particular ZLIB.DLL build, and to use the
87 same one in the new build. If you don't know what this is all
89 DLL intact.
92 4. Can I compile my application using the new zlib interface, and
93 link it to an old ZLIB.DLL, that was built from zlib-1.1.4 or
97 what kind of ZLIB.DLL you have. Even if you are lucky, this
98 course of action is unreliable.
101 version of zlib (post- 1.1.4), it is strongly recommended to
102 link it to the new ZLIB1.DLL.
105 5. Why are the zlib symbols exported by name, and not by ordinal?
108 is risky. Any single glitch in the maintenance or use of the
110 builds and frustrating crashes. Simply put, the benefits of
111 exporting symbols by ordinal do not justify the risks.
114 the DEF file, and still export the symbols by name. Ordinals
117 hints, for a faster name lookup. However, if the DEF file
120 those ordinals, and not the names. It is interesting to
122 problem.
126 source files. You can do this in zlib by predefining the
127 ZLIB_DLL macro.
130 6. I see that the ZLIB1.DLL functions use the "C" (CDECL) calling
131 convention. Why not use the STDCALL convention?
138 refer to the convention triggered by "__fastcall".)
142 Win32), but the standard C functions use CDECL. If a user
143 application is intrinsically tied to the Windows API (e.g.
146 WINAPI. But if ANSI C or POSIX portability is a goal (e.g.
148 sound decision to request the inclusion of <windows.h>, or to
150 functions STDCALL-able.
153 "Windows functionality", but is more like "C functionality".
157 functions, just like CDECL. It is unfortunate that, in spite
159 convention used by the C compilers that run under Windows.
162 are not specified; but that is another story for another day.
164 The remaining fact is that CDECL is the default convention.
166 prototypes inside C headers, problems may appear. The
168 of these problems.
171 zlib in other programming languages. Some of them, like Ada
173 initially on Unix, and relying on the C calling convention.
174 On the other hand, the pre- .NET versions of Microsoft Visual
176 it does not require, FASTCALL.
179 programming language, we choose the default "C" convention.
181 encouraged to maintain specialized projects. The "contrib/"
183 of foreign bindings, such as Ada, C++, and Delphi.
186 7. I need a DLL for my Visual Basic project. What can I do?
188 - Define the ZLIB_WINAPI macro before including "zlib.h", when
191 Basic). The ZLIB_WINAPI macro will switch on the WINAPI
192 (STDCALL) convention. The name of this DLL must be different
193 than the official ZLIB1.DLL.
195 Gilles Vollant has contributed a build named ZLIBWAPI.DLL,
197 functionality built in. For more information, please read
198 the notes inside "contrib/vstudio/readme.txt", found in the
199 zlib distribution.
202 8. I need to use zlib in my Microsoft .NET project. What can I
205 - Henrik Ravn has contributed a .NET wrapper around zlib. Look
206 into contrib/dotzlib/, inside the zlib distribution.
209 9. If my application uses ZLIB1.DLL, should I link it to
210 MSVCRT.DLL? Why?
213 application to MSVCRT.DLL, if it uses ZLIB1.DLL.
215 The executables (.EXE, .DLL, etc.) that are involved in the
216 same process and are using the C run-time library (i.e. they
218 library. There are several libraries in the Win32 system:
219 CRTDLL.DLL, MSVCRT.DLL, the static C libraries, etc.
220 Since ZLIB1.DLL is linked to MSVCRT.DLL, the executables that
221 depend on it should also be linked to MSVCRT.DLL.
224 10. Why are you saying that ZLIB1.DLL and my application should
226 application and my DLLs to different C libraries (e.g. my
227 application to a static library, and my DLLs to MSVCRT.DLL),
228 and everything works fine.
231 <windows.h> and the related headers), its DLL build will work
232 in any context. But if this library invokes standard C API,
233 things get more complicated.
235 There is a single Win32 library in a Win32 system. Every
237 is safe to call from anywhere. On the other hand, there are
239 own separate internal state. Standalone executables and user
241 (CRT) library, be it static or shared (DLL). Intermixing
244 same process.
247 internal states are kept intact. The Microsoft Knowledge Base
250 mention the potential problems raised by intermixing.
254 internal states, maybe by careful design, or maybe by fortune.
256 Also note that linking ZLIB1.DLL to non-Microsoft CRTs, such
257 as those provided by Borland, raises similar problems.
260 11. Why are you linking ZLIB1.DLL to MSVCRT.DLL?
262 - MSVCRT.DLL exists on every Windows 95 with a new service pack
264 on all other Windows 4.x or later (Windows 98, Windows NT 4,
265 or later). It is freely distributable; if not present in the
267 software provider for free.
269 The fact that MSVCRT.DLL does not exist on a virgin Windows 95
270 is not so problematic. Windows 95 is scarcely found nowadays,
273 even run on it. Furthermore, no serious user should run
274 Windows 95 without a proper update installed.
277 12. Why are you not linking ZLIB1.DLL to
282 * Linking ZLIB1.DLL to a static C library (LIBC.LIB, or
283 LIBCMT.LIB) is not a good option. People are using the DLL
284 mainly to save disk space. If you are linking your program
286 in statically, too.
288 * Linking ZLIB1.DLL to CRTDLL.DLL looks appealing, because
289 CRTDLL.DLL is present on every Win32 installation.
292 provide support for 64-bit file offsets, (and so on...),
293 and Microsoft discontinued its support a long time ago.
295 * Linking ZLIB1.DLL to MSVCR70.DLL or MSVCR71.DLL, supplied
296 with the Microsoft .NET platform, and Visual C++ 7.0/7.1,
297 raises problems related to the status of ZLIB1.DLL as a
298 system component. According to the Microsoft Knowledge Base
300 Runtime Component in Visual C++ .NET", MSVCR70.DLL and
301 MSVCR71.DLL are not supposed to function as system DLLs,
302 because they may clash with MSVCRT.DLL. Instead, the
303 application's installer is supposed to put these DLLs
304 (if needed) in the application's private directory.
305 If ZLIB1.DLL depends on a non-system runtime, it cannot
306 function as a redistributable system component.
308 * Linking ZLIB1.DLL to non-Microsoft runtimes, such as
310 reliable presence of these runtimes on Win32 systems.
313 explained in the answer to Question 14.
316 13. If ZLIB1.DLL cannot be linked to MSVCR70.DLL or MSVCR71.DLL,
317 how can I build/use ZLIB1.DLL in Microsoft Visual C++ 7.0
318 (Visual Studio .NET) or newer?
323 system component. That is, it should not be assumed that this
324 runtime exists, or may be installed in a system directory.
325 Since ZLIB1.DLL is supposed to be a system component, it may
326 not depend on a non-system component.
328 In order to link ZLIB1.DLL and your application to MSVCRT.DLL
329 in VC7, you need the library of Visual C++ 6.0 or older. If
331 use ZLIB1.DLL.
335 from the Visual C++ environment. Until then, you have a
336 couple of alternatives, such as linking zlib in statically.
338 as explained in the answer to Question 14.
341 14. I need to link my own DLL build to a CRT different than
342 MSVCRT.DLL. What can I do?
345 it the way you want. You should, however, clearly state that
346 your build is unofficial. You should give it a different file
349 others (i.e. it's neither in the PATH, nor in the SYSTEM or
350 SYSTEM32 directories). Otherwise, your build may clash with
351 applications that link to the official build.
354 CYGWIN1.DLL, and it is distributed under the name CYGZ.DLL.
357 15. May I include additional pieces of code that I find useful,
358 link them in ZLIB1.DLL, and export them?
360 - No. A legitimate build of ZLIB1.DLL must not include code
361 that does not originate from the official zlib source code.
363 file name, as suggested in the previous answer.
366 with Borland Delphi and C++ Builder. The DLL build of VCL
367 is a redistributable file, named VCLxx.DLL.
370 16. May I remove some functionality out of ZLIB1.DLL, by enabling
373 - No. A legitimate build of ZLIB1.DLL must provide the complete
375 code. But you can make your own private DLL build, under a
376 different file name, as suggested in the previous answer.
381 Cosmin Truta <cosmint@cs.ubbcluj.ro>