Minimal rebuilds

[Steve McLellan]

Hi,

We've got two developers working on the same mixed C++ project, using .SLN
and .CPROJ project file (i.e. with identical configurations) on two
different VS .NET 2003. The project files are in CVS. On one machine if you
don't change anything between builds, the compiler recognises this. If you
change one file, it just compiles the minimum necessary. On the other
machine, it's doing a nearly complete rebuild even if NO files have changed.

This is a bit of an annoyance, and I can't figure it out. I've tried
deleting the .IDB file and VC dutifully rebuilt it but it doesn't seem to be
using it. I did notice that with the compiler /clr option you can't also
specify Enable Minimum Rebuild, but I still don't understand how this
behaviour could happen on one machine and not the other.

Any help greatly appreciated.

Steve

 

[Richard Otter]

Check to clock on both machines.

 

[Steve McLellan]

They're both right. In any case, that shouldn't matter - hitting Ctrl +
Shift + B twicde in succession (allowing for the build time) causes two
rebuilds, even if absolutely no changes (either locally or through a CVS
checkout). There's no automatic CVS stuff going on; none of the files on
disk have changed. It's all very puzzling.

Steve

 

[Steve McLellan]

I've checked the clock, and they're both being synchronized with the MS time
server every week and are both in the same time zone (GMT with daylight
saving). Is there no other reason this could be happening? A new project
(which isn't in source control, but I don't know if that's important) doen't
have this problem. I guess it'd be worth setting up a new project using
source controlled files and seeing if that's ok.

Steve

 

[Matt Osborn]

Are one of the source files set to a future date?

 

[Steve McLellan]

No, not as far as I know. The files have all been checked fresh out of CVS
onto two separate machines with their clocks set very similarly, and on one
VS behaves, on the other it doesn't. We may just set up a new user, and do a
completely fresh checkout and VS install, see if that helps anything. It's a
test machine set up to dual boot XP, so that'd be another option. It's still
a pain, and very puzzling.

Steve

 

[Richard Otter]

I would definitly check this for sure.

No, not as far as I know. The files have all been checked fresh out of CVS
onto two separate machines with their clocks set very similarly, and on one
VS behaves, on the other it doesn't. We may just set up a new user, and do a
completely fresh checkout and VS install, see if that helps anything. It's a
test machine set up to dual boot XP, so that'd be another option. It's still
a pain, and very puzzling.

Steve