[Top][All Lists]

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

Re: Attn Dennis Jones: CVS Windows Build, Visual C++ Project Files

From: Dennis Jones
Subject: Re: Attn Dennis Jones: CVS Windows Build, Visual C++ Project Files
Date: Mon, 12 Apr 2004 14:37:31 -0700

----- Original Message ----- 
From: "Conrad T. Pino" <Conrad@Pino.com>
To: "Dennis Jones" <djones@oregon.com>
Cc: "Bug CVS" <bug-cvs@gnu.org>; "Wolfgang Loch" <wolo@wolosoft.com>; "Derek
Robert Price" <derek@ximbiot.com>
Sent: Monday, April 12, 2004 2:00 PM
Subject: RE: Attn Dennis Jones: CVS Windows Build, Visual C++ Project Files

> Hi Dennis,
> First of all, I say let's honor your other priorities.

I appreciate that, and it is what I plan to do (and must do).

> Second, I may have spoken too quickly.  Derek wants to automate absolute
> removal from .dep/.mak files before committing to VC5 to VC6 upgrade.
> also wants to assure we meet your requirements for the nightly build and I
> test enough cases so we don't break anything for you which is why I
> your input.
> However in this case further input from you on this topic won't be needed
> the following align correctly:
> 1. When all VC project files (.dsw .dsp .dep .mak) in CCVS archive are are
> upgraded to VC6, do you see a need for you to use VC5 "Export Makefile..."
> to regenerate a .mak files?

I don't think so.

First, I remember thinking how strange it was that VC5 had no trouble
reading the VC6 project file.  Apparently the project file format didn't
change enough to preclude VC5 form reading it and building CVS successfully
(although there may have been project settings that went unrecognized).  So,
it might not be an issue at all.

Second, it is much less likely that the VC5 command-line tools will have any
difficulty with the makefile (compared to the VC5 IDE having trouble with
the project files).  Thus, I suspect building CVS with the VC5 command-line
tools will continue to work just fine, even if the VC6 project files are
unreadable and/or unrecognized by VC5.

The only potential problem in the future would be if CVS were to make use of
VC6-specific library functions.  However, today that isn't even an issue.

> 2. If Question 1 answer is "Yes", do you want me to check your regenerated
> .mak files for absolute path names such that these cases are covered by an
> automated removal script Derek has proposed?
> 3. If Question 1 answer is "No", do you want to test VC6 project files
> VC5 prior to having them committed to CCVS archive?

Yes, that would probably be smart, just to be safe.

- Dennis

[This E-mail Scanned for viruses by Onlinemac.com]

reply via email to

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