[Zlib-devel] Second zlib 1.2.4 candidate

[Cosmin Truta]

[I'm resending this email, since I accidentally sent it from my Gmail
account, which is not subscribed to zlib-devel, and I'm not sure it
got through the mailing list filters. If you see this for the second
time, please discard it. Apologies...]

---------- Forwarded message ----------
From: Cosmin Truta
Date: Sun, Mar 14, 2010 at 12:03 PM
Subject: Re: [Zlib-devel] Second zlib 1.2.4 candidate
To: zlib-devel at madler.net


On Sun, Mar 14, 2010 at 11:25 AM, Mark Adler wrote:
> On Mar 14, 2010, at 8:20 AM, Cosmin Truta wrote:
>> Works well for me so far, but, Mark, could you please put back the
>> following files:
>> contrib/masmx64/gvmat64.obj
>> contrib/masmx64/inffasx64.obj
>> contrib/masmx86/gvmat32.obj
>> contrib/masmx86/inffas32.obj
>
> Cosmin,
>
> I think I'd rather stick with the convention that there are no object files in the distribution, especially if the assembler is available for free.  Can we put a link for that in the readme files?

Ok, Mark, here is the link to Microsoft MASM 8.0 fox x86:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7a1c9da0-0510-44a2-b042-7ef370530c64

This is for x86 only, so you should only add this link to
contrib/masmx86/readme.txt. The other readme, inside contrib/masmx64,
already has a link to MASM64 (ml64.exe).

> Also the asm files were recently modified for three out of the four of the object files you mention, so I don't have up-to-date object files for those.

Actually, the amount of extra work required to rebuild the .obj files
out of their sources, whenever the sources change, is an even stronger
reason against including the .obj files in the distro. I agree, and
I'm glad that the availability of MASM nowadays makes this a
non-issue.

Best regards,
Cosmin