Re: Devenv 2003: Constant Relinking.
- From: Victor Bazarov <v.Abazarov@xxxxxxxxxxxx>
- Date: Wed, 06 Jul 2005 11:14:22 -0400
ShayEr wrote:
"Victor Bazarov" wrote:ShayEr wrote:
I have a very complicated project that consist of something like 50 static libs, each time that i want to debug the project the environment claims that the .main executable is not up-to-date a needs to be build. Each time that a debugging session starts the compiler relink my project. Is there a way to know which output is not updated? The $(TargetPath) seems on and also the .pdb files and .map files.
It sounds more like one of your libraries or object modules has its datetime stamp waaaay in the future. Rebuild all and see if it changes. Or search the .obj and .lib files and sort by date in the search window, to see which one is in the future. Then rebuild only that one.
V
I've done rebuilds like a gazillion times, and just to make sure I searched the entire directory for *.obj and *.libs from the future.
Is there a way that the compiler tell we why he things that the exe is out of date?
If there is, I don't know about it. Sorry.
Have you tried removing .pdb and .ilk files (and other files you don't know or don't care for)?
V .
- Follow-Ups:
- Re: Devenv 2003: Constant Relinking.
- From: ShayEr
- Re: Devenv 2003: Constant Relinking.
- References:
- Devenv 2003: Constant Relinking.
- From: ShayEr
- Re: Devenv 2003: Constant Relinking.
- From: Victor Bazarov
- Re: Devenv 2003: Constant Relinking.
- From: ShayEr
- Devenv 2003: Constant Relinking.
- Prev by Date: Convert VC6 workspace to VC7
- Next by Date: Re: Convert VC6 workspace to VC7
- Previous by thread: Re: Devenv 2003: Constant Relinking.
- Next by thread: Re: Devenv 2003: Constant Relinking.
- Index(es):
Relevant Pages
|
Loading