From: JonY <10...@gm...> - 2008-11-09 04:58:39
|
On 11/9/2008 12:35, sowiso wrote: > ----- Original Message ----- > From: "JonY"<10...@gm...> > To: "MinGW Users List"<min...@li...> > Sent: Sunday, November 09, 2008 4:29 AM > Subject: Re: [Mingw-users] Problems in compiling zlib into my app (using > mingw + msys) > >>> I know it that far :) However, although I've tried to rename the >>> blah.zip to blah.gz, WinRAR refused to unpack it. >>> I reckon the team should put things like this in the FAQ to not > confuse >>> newbies. >>> >> Hmm, at this point, I'm not even sure if its gzip. > > You can't be. It appears to be a special format which is simply > targeting on even better speed and performance. > I found out more in the zlib faq, link bellow. >> Are you sure those are make targets? They look like dependencies. >> >> iirc, zlib doesn't use autotools at all. The Makefile you saw was >> designed to link with libz.a (the static library) which is the created >> when "make" was run in the root directory. > > I thought that too. However, I know it better :-) > The contrib tools absolutely require iowin32.c on windows. > Just go from the root directory and do a search for iowin32.c. > You will only find references to this file either in the contrib/minizip > directory, or in its subdirectory where you can find VC project files. > Yes, I did look closely. Those contrib tools are NOT touched (and not > able to get compiled) when make'ing from the root directory. > You cannot make them from there. Either you are using Visual Studio > (where project files are provided), or you are on your own (just as I > was). > I think you're supposed to run "make" in the root first, then run "make" in the contrib directories. >>> I could only know that because I was LUCKY to have programmed a tool >>> which needs several *.c files, and thus know what to pass gcc at the >>> command line. >>> However, for any beginner, this is doomed to fail with THIS > wonderful >>> kind of "documentation." >>> But somehow the mailing lists must be kept busy, huh? :P >>> >> I don't think I understand your request, which "documentation" are you >> referring to? The gcc parameters are already in the gcc docs. > > The "comprehensive" documentation found in the zlib package, for > example. I found <http://www.zlib.net/zlib_faq.html>. It does explain about gzip and pkzip briefly. |