diff options
| author | Mark Adler <madler@alumni.caltech.edu> | 2024-01-17 17:19:03 -0800 |
|---|---|---|
| committer | Mark Adler <madler@alumni.caltech.edu> | 2024-01-17 17:19:03 -0800 |
| commit | 25263462377fa5c569947a40315815bd59e37f4b (patch) | |
| tree | 629ecaa51b17c14ab7de8696e2db312f43e1ff92 | |
| parent | fe41d1892117fa81bd49f69b1c87d805635b853c (diff) | |
| download | zlib-25263462377fa5c569947a40315815bd59e37f4b.tar.gz zlib-25263462377fa5c569947a40315815bd59e37f4b.tar.bz2 zlib-25263462377fa5c569947a40315815bd59e37f4b.zip | |
Remove mentions of an official zlib DLL distribution.
There used to be one, but no more. It is up to the user or vendor
to compile zlib.
| -rw-r--r-- | FAQ | 3 | ||||
| -rw-r--r-- | win32/DLL_FAQ.txt | 20 |
2 files changed, 3 insertions, 20 deletions
| @@ -14,8 +14,7 @@ The latest zlib FAQ is at http://zlib.net/zlib_faq.html | |||
| 14 | 2. Where can I get a Windows DLL version? | 14 | 2. Where can I get a Windows DLL version? |
| 15 | 15 | ||
| 16 | The zlib sources can be compiled without change to produce a DLL. See the | 16 | The zlib sources can be compiled without change to produce a DLL. See the |
| 17 | file win32/DLL_FAQ.txt in the zlib distribution. Pointers to the | 17 | file win32/DLL_FAQ.txt in the zlib distribution. |
| 18 | precompiled DLL are found in the zlib web site at http://zlib.net/ . | ||
| 19 | 18 | ||
| 20 | 3. Where can I get a Visual Basic interface to zlib? | 19 | 3. Where can I get a Visual Basic interface to zlib? |
| 21 | 20 | ||
diff --git a/win32/DLL_FAQ.txt b/win32/DLL_FAQ.txt index 12c0090..d8cf5f3 100644 --- a/win32/DLL_FAQ.txt +++ b/win32/DLL_FAQ.txt | |||
| @@ -3,7 +3,7 @@ | |||
| 3 | 3 | ||
| 4 | 4 | ||
| 5 | This document describes the design, the rationale, and the usage | 5 | This document describes the design, the rationale, and the usage |
| 6 | of the official DLL build of zlib, named ZLIB1.DLL. If you have | 6 | of the common DLL build of zlib, named ZLIB1.DLL. If you have |
| 7 | general questions about zlib, you should see the file "FAQ" found | 7 | general questions about zlib, you should see the file "FAQ" found |
| 8 | in the zlib distribution, or at the following location: | 8 | in the zlib distribution, or at the following location: |
| 9 | http://www.gzip.org/zlib/zlib_faq.html | 9 | http://www.gzip.org/zlib/zlib_faq.html |
| @@ -11,13 +11,9 @@ in the zlib distribution, or at the following location: | |||
| 11 | 11 | ||
| 12 | 1. What is ZLIB1.DLL, and how can I get it? | 12 | 1. What is ZLIB1.DLL, and how can I get it? |
| 13 | 13 | ||
| 14 | - ZLIB1.DLL is the official build of zlib as a DLL. | 14 | - ZLIB1.DLL is the common build of zlib as a DLL. |
| 15 | (Please remark the character '1' in the name.) | 15 | (Please remark the character '1' in the name.) |
| 16 | 16 | ||
| 17 | Pointers to a precompiled ZLIB1.DLL can be found in the zlib | ||
| 18 | web site at: | ||
| 19 | http://www.zlib.net/ | ||
| 20 | |||
| 21 | Applications that link to ZLIB1.DLL can rely on the following | 17 | Applications that link to ZLIB1.DLL can rely on the following |
| 22 | specification: | 18 | specification: |
| 23 | 19 | ||
| @@ -379,18 +375,6 @@ in the zlib distribution, or at the following location: | |||
| 379 | code. But you can make your own private DLL build, under a | 375 | code. But you can make your own private DLL build, under a |
| 380 | different file name, as suggested in the previous answer. | 376 | different file name, as suggested in the previous answer. |
| 381 | 377 | ||
| 382 | |||
| 383 | 17. I made my own ZLIB1.DLL build. Can I test it for compliance? | ||
| 384 | |||
| 385 | - We prefer that you download the official DLL from the zlib | ||
| 386 | web site. If you need something peculiar from this DLL, you | ||
| 387 | can send your suggestion to the zlib mailing list. | ||
| 388 | |||
| 389 | However, in case you do rebuild the DLL yourself, you can run | ||
| 390 | it with the test programs found in the DLL distribution. | ||
| 391 | Running these test programs is not a guarantee of compliance, | ||
| 392 | but a failure can imply a detected problem. | ||
| 393 | |||
| 394 | ** | 378 | ** |
| 395 | 379 | ||
| 396 | This document is written and maintained by | 380 | This document is written and maintained by |
