Lines Matching full:dll
2 Frequently Asked Questions about ZLIB1.DLL
6 of the official DLL build of zlib, named ZLIB1.DLL. If you have
12 1. What is ZLIB1.DLL, and how can I get it?
14 - ZLIB1.DLL is the official build of zlib as a DLL.
17 Pointers to a precompiled ZLIB1.DLL can be found in the zlib
21 Applications that link to ZLIB1.DLL can rely on the following
30 * The ZLIB1.DLL binary is linked to MSVCRT.DLL.
32 The archive in which ZLIB1.DLL is bundled contains compiled
33 test programs that must run with a valid build of ZLIB1.DLL.
34 It is recommended to download the prebuilt DLL from the zlib
37 and build settings. If you do build the DLL yourself, please
40 the original ZLIB1.DLL distribution.
42 If, for any reason, you need to build an incompatible DLL,
46 2. Why did you change the name of the DLL to ZLIB1.DLL?
47 What happened to the old ZLIB.DLL?
49 - The old ZLIB.DLL, built from zlib-1.1.4 or earlier, required
51 a static build. The DLL settings were supposed to be enabled
57 the DLL, not all people added it to the build options. In
58 consequence, incompatible incarnations of ZLIB.DLL started
62 DLL, applications had to define the ZLIB_DLL macro and
65 that were unable to run with the official ZLIB.DLL build.
68 a binary-incompatible change in the DLL interface, in order to
70 the new DLL under a different name.
72 We chose the name ZLIB1.DLL, where '1' indicates the major
78 efficient build and use of the DLL, but compatibility no
82 3. Can I build ZLIB.DLL from the new zlib sources, and replace
83 an old ZLIB.DLL, that was built from zlib-1.1.4 or earlier?
87 it depends on what you mean by "an old ZLIB.DLL", because the
88 old DLL exists in several mutually-incompatible versions.
90 being used in your particular ZLIB.DLL build, and to use the
93 DLL intact.
97 link it to an old ZLIB.DLL, that was built from zlib-1.1.4 or
101 what kind of ZLIB.DLL you have. Even if you are lucky, this
106 link it to the new ZLIB1.DLL.
119 exist in every DLL, and even if the dynamic linking performed
120 at the DLL startup is searching for names, ordinals serve as
134 6. I see that the ZLIB1.DLL functions use the "C" (CDECL) calling
190 7. I need a DLL for my Visual Basic project. What can I do?
193 building both the DLL and the user application (except that
194 you don't need to define anything when using the DLL in Visual
196 (STDCALL) convention. The name of this DLL must be different
197 than the official ZLIB1.DLL.
199 Gilles Vollant has contributed a build named ZLIBWAPI.DLL,
213 9. If my application uses ZLIB1.DLL, should I link it to
214 MSVCRT.DLL? Why?
217 application to MSVCRT.DLL, if it uses ZLIB1.DLL.
219 The executables (.EXE, .DLL, etc.) that are involved in the
223 CRTDLL.DLL, MSVCRT.DLL, the static C libraries, etc.
224 Since ZLIB1.DLL is linked to MSVCRT.DLL, the executables that
225 depend on it should also be linked to MSVCRT.DLL.
228 10. Why are you saying that ZLIB1.DLL and my application should
231 application to a static library, and my DLLs to MSVCRT.DLL),
235 <windows.h> and the related headers), its DLL build will work
240 function in this library resides in a single DLL module, that
245 (CRT) library, be it static or shared (DLL). Intermixing
247 DLL are linked to different CRTs, and both are running in the
260 Also note that linking ZLIB1.DLL to non-Microsoft CRTs, such
264 11. Why are you linking ZLIB1.DLL to MSVCRT.DLL?
266 - MSVCRT.DLL exists on every Windows 95 with a new service pack
273 The fact that MSVCRT.DLL does not exist on a virgin Windows 95
281 12. Why are you not linking ZLIB1.DLL to
286 * Linking ZLIB1.DLL to a static C library (LIBC.LIB, or
287 LIBCMT.LIB) is not a good option. People are using the DLL
292 * Linking ZLIB1.DLL to CRTDLL.DLL looks appealing, because
293 CRTDLL.DLL is present on every Win32 installation.
299 * Linking ZLIB1.DLL to MSVCR70.DLL or MSVCR71.DLL, supplied
301 raises problems related to the status of ZLIB1.DLL as a
304 Runtime Component in Visual C++ .NET", MSVCR70.DLL and
305 MSVCR71.DLL are not supposed to function as system DLLs,
306 because they may clash with MSVCRT.DLL. Instead, the
309 If ZLIB1.DLL depends on a non-system runtime, it cannot
312 * Linking ZLIB1.DLL to non-Microsoft runtimes, such as
315 It's easier to let the DLL build of zlib up to the people
320 13. If ZLIB1.DLL cannot be linked to MSVCR70.DLL or MSVCR71.DLL,
321 how can I build/use ZLIB1.DLL in Microsoft Visual C++ 7.0
329 Since ZLIB1.DLL is supposed to be a system component, it may
332 In order to link ZLIB1.DLL and your application to MSVCRT.DLL
335 use ZLIB1.DLL.
345 14. I need to link my own DLL build to a CRT different than
346 MSVCRT.DLL. What can I do?
348 - Feel free to rebuild the DLL from the zlib sources, and link
358 CYGWIN1.DLLDLL.
362 link them in ZLIB1.DLL, and export them?
364 - No. A legitimate build of ZLIB1.DLL must not include code
366 But you can make your own private DLL build, under a different
370 with Borland Delphi and C++ Builder. The DLL build of VCL
371 is a redistributable file, named VCLxx.DLL.
374 16. May I remove some functionality out of ZLIB1.DLL, by enabling
377 - No. A legitimate build of ZLIB1.DLL must provide the complete
379 code. But you can make your own private DLL build, under a
383 17. I made my own ZLIB1.DLL build. Can I test it for compliance?
385 - We prefer that you download the official DLL from the zlib
386 web site. If you need something peculiar from this DLL, you
389 However, in case you do rebuild the DLL yourself, you can run
390 it with the test programs found in the DLL distribution.
