httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@lnd.com>
Subject RE: MS VC++ with 2.0
Date Tue, 25 Apr 2000 22:55:30 GMT
> From: rbb@covalent.net [mailto:rbb@covalent.net]
> Sent: Tuesday, April 25, 2000 2:24 PM
>
> As promised, here are the diffs for the 6.0 dsp's.  It looks like the
> changes are inconsequential, but if we go to 6.0, then the
> people using
> 5.0 will have to mung their files to read 6.0, or if we stick
> with 5.0,
> people using 6.0 have to munge their files.  This is really
> annoying.  :-(


> Index: src/Apache.dsp
> ===================================================================
> RCS file: /home/cvs/apache-2.0/src/Apache.dsp,v
> retrieving revision 1.5
> diff -u -r1.5 Apache.dsp
> --- src/Apache.dsp	2000/04/17 13:56:38	1.5
> +++ src/Apache.dsp	2000/04/25 20:58:24
> @@ -1,5 +1,5 @@
>  # Microsoft Developer Studio Project File - Name="Apache" -
> Package Owner=<4>
> -# Microsoft Developer Studio Generated Build File, Format Version 5.00
> +# Microsoft Developer Studio Generated Build File, Format Version 6.00
>  # ** DO NOT EDIT **
>
>  # TARGTYPE "Win32 (x86) Console Application" 0x0103
> @@ -22,6 +22,7 @@
>  !MESSAGE
>
>  # Begin Project
> +# PROP AllowPerConfigDependencies 0
>  # PROP Scc_ProjName ""
>  # PROP Scc_LocalPath ""
>  CPP=cl.exe

These changes harm nothing, everything still builds.  If the .dsp project is then saved in
5.0, the AllowPerConfigDependencies tag
is removed and the format reverts to 5.00.  I can see no other effects.  I don't really care
either way, as long as we are clear we
don't start flipping 6.0 specific options, and therefore break vc5 builds.


Mime
View raw message