> The actual compressed data in a pkzip file is the same thing.
> You have to use MAX_WBITS (I think that's the one) set to -1 to
> prevent some table from getting created/looked for.
I suspected it might be the case, but I could not find any explicit
of it in the zlib tar file that I downloaded. What threw me off totally
when I saw that the build actually created a small foo.gz test file as
Are you really saying that .zip and .gz files are essentially the same?
Then why the different extensions? Besides, the unzip program can't even
unzip the foo.gz; it complains about some "End-of-central-directory
not found." problem. The "gunzip" program, however, had no problem with
I also checked all the references to MAX_WBITS in the source but there is
no mention there anything about what value to choose for .gz or .zip file
format. Then I checked all references to PKZIP but I only found a three
source files with some conditional compile based on
condition. Now, I could probably figure out more by wading through the
code, but I just don't have that kind of time, not to mention that much
of it is probably way over my head. :-(
Quote:> The file
> that explains zip internal format is available on the web and I'm sure
> I found it starting at the "official zlib home page" at
> http://www.cdrom.com/pub/infozip/zlib/ but don't remember the exact
> url of the format description.
Yes, I've seen it, but I was hoping that I would not have to go down to
that level. What I mean is that I just wanted to specify what files I
wanted to archive into what zip file and there would be some zlib function
that would take it from there. If I can't do this with a zlib function
I might as well adapt the stand-alone zip source code to do this for me,
essentially seeing what function the main() is calling for what command
line options. I really don't have the time or even the desire to be a
file compression expert for this one-time short project. It would not be