From: Keith M. <kei...@to...> - 2007-05-03 11:53:11
|
Vincent Torri wrote, quoting Charles Wilson: >>> I also changed the name zlib1.dll to a more classic name : libz-1.dll >> >> This is good -- and bad. According to http://www.zlib.net/DLL_FAQ.txt the >> name 'zlib1.dll' is reserved explicitly for a zlib DLL compiled in a specific >> manner, guaranteeing compatibility for win32 users who just want to download >> the DLL itself. Otherwise, system integrators are asked to use a name other >> than 'zlib1.dll'. >> >> However, I believe that mingw's zlib dll *is* compiled in the correct manner, >> and should be interface-compatible with the official zlib dll. So, we *could* >> use the 'zlib1.dll' name if we choose to. > > ok. I can make the patch without changing the lib name. Keith, would it be > good for you ? If it is *guaranteed* 100% ABI compatible with the official binary download from zlib.net, then I don't see any problem; have you tried running their test suite, from the official build package, to confirm this? Do we really gain anything by building this ourselves, rather than just grabbing the official build from any of: http://www.zlib.net/zlib123-dll.zip http://www.gzip.org/zlib/zlib123-dll.zip, or http://prdownloads.sourceforge.net/libpng/zlib123-dll.zip?download If not, what's the rationale for offering this as a mingwPORT? Regards, Keith. |