[Zlib-devel] zlib 1.2.7 released

[Jan Nijtmans]

2012/9/6 Daniel Richard G. <oss at teragram.com>

> Why not build the DLL using a MinGW environment? MinGW has always targeted
> good ol' MSVCRT.DLL, for licensing reasons.
>

That's what I did, the dll can best be built with the MinGW environment.
I'm only talking about zdll.lib, It cannot be built with MinGW.


> And if an undesired linkage with msvcrXX.dll is generated, that probably
>> can be fixed with the option -nodefaultlib.
>>
>
> Won't work. You could force the linker to ignore MSVCR##.DLL and link
> against MSVCRT.DLL, but then you're at the mercy of all the
> implementation-dependent aspects of the C runtime not lining up (symbols in
> macro expansions, publicly-exposed structs, newer compiler intrinsics,
> etc.).
>

Well, I tried the command
       lib -machine:X64 -name:zlib1.dll -def:zlib.def -out:zdll.lib
-nodefaultlib
(on VS10, using a 64-bit zlib1.dll compiled with MinGW-w64 64-bit compiler)
and then tried if MinGW-w64 could use it for final linking. It looks like
its
working! The "depends" utility is not showing any dependancy on
MSVCR##.DLL, only MSVCRT.DLL as it should be, even though I'm using VS10.
Will do more testing.........

Regards,
          Jan Nijtmans
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://madler.net/pipermail/zlib-devel_madler.net/attachments/20120906/421e4f76/attachment.html>