[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MS Visual C++ Version

From: Eric Siegerman
Subject: Re: MS Visual C++ Version
Date: Thu, 10 May 2001 21:02:31 -0400
User-agent: Mutt/1.2.5i

On Sun, May 06, 2001 at 01:58:16PM -0400, Laine Stump wrote:
> It doesn't. VC4 uses makefiles (.mak), VC5 and VC6 use project and
> workspace files (.dsp and .dsw).

This is known as "progress".  Not!

Why not provide both versions?
  - Make a subdirectory for each VC++ version and put that
    version's funky project/workspace/makefile/xml/whatever's in

  - Add a step to the documentation for building CVS on a WinXX
    system: copy the devkit-specific files from the appropriate
    subdirectory to <wherever the devkit will look for them>.

  - Explicitly disclaim any promises to keep old versions up to
A good way to do that last would be to move the build files for
old versions of VC++ to contrib, and keep only the files for the
current version in the main CVS distribution.  Or, more
generally, "bless" exactly one VC++ version -- whether the most
recent or an older one.  Keep the blessed version's files in the
main distribution, and move the rest to contrib.

> I think that whoever is donating the time to maintain the make/project
> files for VC should do it in whatever format is the most convenient
> for them, and everyone else should either live with it, or donate
> *their* time to supply project files for the older/newer versions.

This is a good criterion for determining which VC++ version to
bless at any given time.


|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea.
        - RFC 1925 (quoting an unnamed source)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]