[Zlib-devel] new assembly code for modified structure inzLib1.2.2.1

[Andrei Polushin]

----- Original Message ----- 
From: "Mark Adler" <madler at alumni.caltech.edu>
Sent: Tuesday, January 04, 2005 11:19 AM
> On Jan 3, 2005, at 3:34 PM, Gilles Vollant wrote:
> >  in zlib 1.2.2.2, you've successfully updated gvmat32.asm and
> > inffas32.asm
> > in contrib\masmx86, but I found old gvmat32.obj and inffas32.obj in
> > contrib\vstudio\vc7
> > I suggest you update the .obj in  contrib\vstudio\vc7 with obj from
> > http://gvollant.free.fr/newasmzl1221.zip
>
> Or how about I just delete the object files?  Is there a reason that
> there needs to be object files in the zlib source distribution?

Probably, the only reason was that the original distribution of MS Visual
Studio 6.0 did not contain MASM - assembler program, ml.exe, so user needs
to download MASM as part of Visual C++ Processor Pack from
http://msdn.microsoft.com/vstudio/downloads/tools/ppack/download.aspx

This is not an issue for Visual Studio 7.0 and later - it contains MASM by
default.

Current zlib distribution contains three projects that explicitly depend on
.obj files:
- two VC70 projects (at contrib/vstudio/vc7/zlib*.vcproj),
- one VC60 project (at projects/visualc6/zlib.dsp).

It might be better for VC70 projects to compile .asm files directly, using a
'Custom Build Step' feature. Those .asm files should be included in projects
with the following settings:
- Description:   Assembling=> $(InputPath)
- Command Line:   ml /nologo /Zi /c /coff /Fo"$(IntDir)"\ "$(InputPath)"
- Outputs:   $(IntDir)\$(InputName).obj
    (In case of problems, Gilles might look at my refused project files).

For VC60 project, the same steps are also applicable, but there should be a
notice in projects/visualc6/README.txt that will direct user to download
MASM (URL above).

// Andrei