[Zlib-devel] MSVC++ projects

[Mark Adler]

Andrei,

Thank you for your work on this.  I would like to incorporate it into 
the distribution.

On Sep 20, 2004, at 12:54 AM, Andrei Polushin wrote:
> These projects are expected to be in the top-level win32 directory.

I don't want to replace the current win32 directory with yours, since 
then useful stuff that's there would be lost, especially Cosmin's DLL 
FAQ.  Can/should they be integrated?

> I think we have to eliminate "projects" directory, because it is not
> dedicated to any platform, as other top-level directories are. It 
> might be
> confusing if "projects" directory will contain both Win32 and Mac 
> projects,
> thus replicating top-level directory layout.

I agree with Cosmin's rationale for a projects directory, copied below. 
  I actually find the platform subdirectories more confusing, since 
there are usually several different compilers and IDE's available on 
any platform.  In the long run, I think all of that should go in 
projects.

Ideally your VC stuff should be in the projects directory.  Are your 
makefiles dependent on what subdirectory of the zlib distribution 
they're in?

mark


On May 31, 2004, at 5:05 AM, Cosmin Truta wrote:
> I would like to propose the addition of a "projects" directory inside
> the zlib distribution. The purpose is to store project files coming 
> from
> various integrated environments (IDE).
>
> The reason to put project files into a separate directory, rather than
> the directory of the platform on which the IDE is running, is that many
> IDE's are cross-platform. For example: Borland C++ (DOS/Windows/Unix),
> RHIDE (DOS/Windows/Unix), Eclipse (many platforms), etc. Even if a
> certain IDE is known to run on a single platform, the project files
> could be used on a newer IDE version, that runs on a different 
> platform;
> e.g. Borland IDE's have such a history.
>
> If we impose the restriction that the binaries built by the projects
> should be entirely compatible to those built by the existing makefiles,
> then these projects may be even used to provide official builds.
>
>
> Simon-Pierre Cadieux and I have worked on a set of project files for
> MS Visual C++ 6.0, that build zlib exactly as win32/Makefile.msc, and
> provide all the build options (static lib or DLL, with or without ASM,
> with or without debugging info) only at one or two clicks away from 
> each
> other. Although there is already a project for Visual C++ in
> contrib/vstudio, that one has to stay in place, because it adds the
> extra minizip functionality.