Unnecessary Recompiles and Relinks

[mattintelnetfort]

We've recently migrated our Compaq project to Intel (V9.0.30). When I build a solution within Visual Studio 2003, fortran projects are doing unnecessary compiles and relinks. How can I prevent this? It seems inconsistent as in some cases only some of the source files in a project get recompiled (i.e., not all), similarly only some projects get relinked. This occurs even if I simply hit the build button on studio (not rebuild), then press it again after the initial build completes (i.e., I've done nothing to update a dependency).

Also, can someone tell me what components of Visual Studio the Intel Visual Fortran Compiler requires? We have a user who will only use the compiler from the command line, and I'd like to save the Studio license; is it possible to install Visual Fortran Compiler without Visual Studio?

[Steven_L_Intel1]

Are your sources or objects on a network share? Time skews can sometimes cause this problem.

The minimum you must install is Visual C++ 2005 Express Edition, which is free, if you install Intel Fortran 9.0.030 or later and want to use the command line only. 9.0.030 can be downloaded from Intel Premier Support File Downloads.

[mattintelnetfort]

Thanks for the clarification on the versions and Visual Studio requirements.

On the unnecessary recompiles, all source files are on the local machine so there should be only a single time source (i.e., clock) involved. I do have many of the files in sourcesafe for configuration management but I see no pattern there.

[Les_Neilson]

You mention sourcesafe. A similar recompiling problem I had was caused by me changing some project setting in every project. This meant I had to check out every vfproj file from Sourcesafe. Unfortunately I just did the change and checked the file back in again, without doing a build. This caused every project to recompile fully even if no code hadchanged. There was a flag set in the project files saying the project settings had changed which forced the recompile every time. I had to manually go through each project again, check out the project file, build,and *then* check the file back into Sourcesafe.

Les

[forall]

I get such unnecessary re-compiles and re-links without any usage of Sourcesafe or similar products. For me it just tends to occur when the number of module exceeds some level of complexity. Amuzingly, it tends to depend on whether I delete the debug/release folders prior to the compilation, whether I do full rebuild etc, and similar idiosyncracies. It's been happening over the last 4 years over many versions of CVF/IVF, many different computers and OS's, so I just live with it now :-)

[adleonard]

I just installed the 9.1 compiler and Visual Studio 2005. I have a solution converted from CVF that has 28 projects. The vfproj files are all in SourceSafe. When I try to build I get error messages on at least some of the projects if the vfproj files are not checked out because they are not writeable. If I check them out and compare the changes after I finish the build and save all the files, it looks like lines only got reordered, but the content didn't really change. Is there a way around this?

[mattintelnetfort]

I am using the 9.1.025 and am seeing the same problem. Has anyone determined a resolution to this problem. I only see the problem in release builds not in debug builds. The project builds successfully, but at the end of the build I get flagged that Visual Studio wants to check out the VFPROJ file from sourcesafe because it's not writeable.