visual studio compile rules

[jchiller]

All,

Does anyone know if there is a way to get Visual Studio to display the
reason it is compiling a file during a build? For example, I start a
build on Project A and Visual Studio determines it needs to compile
file xyz.cpp b/c the source file is newer then the object file. So
ideally the Output window would display something saying the source is
out of date or that a header file the source includes is newer then
the object file.

I have a project that seems to rebuild alot more then it should and
would like to know why. I would like a way examine the reasons why
Visual Studio compiles what it does during a build. Any suggestions
would be appreciated. Thanks in advance.

 

[Kyle Alons]

I don't think that information is exposed. Here some common reasons for
that sort of behavior:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q326946

http://groups.google.com/groups?q=k...TF-8&selm=#aAQ#xmMCHA.2400@tkmsftngp11&rnum=1

http://groups.google.com/[email protected]&rnum=1

 

[Gus McNaughton]

I've just moved to 7.1 from 6.0 and had a project that would always re-link
no matter how up-to-date its dependents.
The problem was in "Additional Dependencies" where there was an entry
"OtherLib\Debug\OtherLib" instead of "OtherLib\Debug\OtherLib.lib". The
external references to this library were satisfied by another dependent
pulling in the correct file but a warning would have been nice.
Hope this helps

 

[Rudy Ray Moore]

Gus,

This interests me. Where is "Additional Dependencies"?

Thanks,

Rudy

 

[Rudy Ray Moore]

I found it:

Startup Project Properties
Linker
Input
Additional Dependencies