lib file keeps fully recompiling even when no changes have been made
-
Hi, I'm using Embedded Visual C++ 4.0 for this project so it's a little different than the recent versions of VC++ but by and large it's the same interface, albeit more similar to the older Visual Studio 6.0 from years past. So the problem is this: I have a large project that consists of several smaller projects. One of these smaller projects, a lib project, keeps fully recompiling every darned time I compile the project, even though no changes have been made to it. The other lib files are fine, they don't recompile unless I change one of their cpp/h files. I'm sure it's just some silly setting on this lib project but for the life of me I can't find it. Does anyone know what I can do to stop it from recompiling every time? Thanks!
KR
-
Hi, I'm using Embedded Visual C++ 4.0 for this project so it's a little different than the recent versions of VC++ but by and large it's the same interface, albeit more similar to the older Visual Studio 6.0 from years past. So the problem is this: I have a large project that consists of several smaller projects. One of these smaller projects, a lib project, keeps fully recompiling every darned time I compile the project, even though no changes have been made to it. The other lib files are fine, they don't recompile unless I change one of their cpp/h files. I'm sure it's just some silly setting on this lib project but for the life of me I can't find it. Does anyone know what I can do to stop it from recompiling every time? Thanks!
KR
Is there some way of showing a verbose listing of what the build system's doing? It might tell you what file(s) it's looking for that's causing the rebuild? Alternatively (and this is something I've done with VS2003/8), you could use SysInternals ProcMon to see what files the build system (msdev for eVC++4?) is accessing - you may well see it looking for files that a) don't exist, and b) aren't built by the build command for some reason. HTH!
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
-
Hi, I'm using Embedded Visual C++ 4.0 for this project so it's a little different than the recent versions of VC++ but by and large it's the same interface, albeit more similar to the older Visual Studio 6.0 from years past. So the problem is this: I have a large project that consists of several smaller projects. One of these smaller projects, a lib project, keeps fully recompiling every darned time I compile the project, even though no changes have been made to it. The other lib files are fine, they don't recompile unless I change one of their cpp/h files. I'm sure it's just some silly setting on this lib project but for the life of me I can't find it. Does anyone know what I can do to stop it from recompiling every time? Thanks!
KR
Check the dates on the lib-project source files. If (for some reason) they're in the future, the compiler will think the object and lib files are always out of date. I've seen a similar problem when the computer's system date is in the past. The new object and lib files get this old date, so always appear out of date. If the lib project uses a DLL with a future date, this can give the same symptoms. Another guess: The dependencies may not be set up correctly for this lib project.
-
Is there some way of showing a verbose listing of what the build system's doing? It might tell you what file(s) it's looking for that's causing the rebuild? Alternatively (and this is something I've done with VS2003/8), you could use SysInternals ProcMon to see what files the build system (msdev for eVC++4?) is accessing - you may well see it looking for files that a) don't exist, and b) aren't built by the build command for some reason. HTH!
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
Oops, sorry I forgot to respond to this but I did actually fix it, the project that kept recompiling was looking for files from a project that weren't added into my parent project. I guess somehow since the one sub-project wasn't added into the parent, the files weren't registering as having been compiled "under the project" or something. When I added in the dependant project, everything was fixed.
KR