compiling source files in a certain sequence

[dnoack]

Hello,
I have just upgraded my CVF 6 to

Intel Fortran Compiler Integration for Microsoft Visual Studio 2005, Version 10.0.3718.2005

and would like to rebuild my existing program library. This library contains module files, which should be compiled first in order to satisfy the references in the other program units. With CVF 6 this was not a problem, but with Visual Studio 2005/Intel Visual Fortran I get the error message

Error 1 Error: Error in opening the compiled module file. Check INCLUDE paths. [MOD_MATH]

It seems that the referenced module should be compiled before the program unit that
yields the error. With CVF 6 I can compile any file separately in any order. But the
new Microsoft Visual Studio 2005 has only the options "build solution" and "build work", but not build file.

How can I define the sequence for building the program units?

Thank you in advance.
Dieter

[Jugoslav_Dujic]

Well, you can compile a single file -- right-click it in the SolutionExplorer and select "compile". Also, you can drag the "compile" command from Tools/Customize/Build to the "Build" menu and/or the toolbar, and assign it a shortcut key (Ctrl+F7, like in the good ol' days).

Just like CVF, the compiler should figure out the correct build order, though (and even better, in case of multiple interdependent modules). Have you tried "rebuild all" first?

Off topic:

Error: Error in opening the compiled module file. Check INCLUDE paths.

I see the error message is changed, finally. Intel folks, good job!

[Steven_L_Intel1]

I would have expected the build order to be determined automatically - if Jugoslav's recommendation does not help, please create a ZIP of the solution and source files and attach it to a problem report submitted to Intel Premier Support.

I too had had enough of the misleading "module library file" message and got it changed.

[dnoack]

Hello Jugoslav,
thank you for the hint. But unfortunatly in IVF10 there no "compile" option available, neither in the context menue for the solution explorer, nor in Tools/Customize/Build. There is also no "rebuild all" option available. Instead there are options "build/rebuild solution" and "build/rebuild work" available.

Of course, I have first tried to rebuild the complete program as with CVF6. I think also, that the compiler figures out the correct build order. But I can see, that one module is not compiled although another program unit needs this module and therefore further building terminates. It seems, that the only possibility is, to compile some modules manually with a command line ifort... . Or have you another hint?

Dieter

[Paul_Curtis]

Steve says, "I would have expected the build order to be determined automatically"

Me too. As the OP noted, this was always the case for CVF, but dependency checking has NEVER WORKED with IVF, not ever, not from the very first IVF edition, and it still doesn't work.

I have filed this as an "issue" with Premier Support many times, with no response. This has been mentioned in this Forum many times, and acknowledged as a continuing problem, but evidently one that has a very low priority within Intel.

[Steven_L_Intel1]

To the best of my knowledge, there are no known problems with the build dependency checking in IVF. We know of many such problems with CVF. When I get back to the office on Monday I'll try looking for Paul's reports to see what happened. Paul, do you have a six-digit issue number I can look for?

I build probably a dozen different projects each day, and have not seen a dependency problem in at least two years now.

[Steven_L_Intel1]

Paul,

I was able to locate only one report by you of issues with the dependency checking, from late 2004. This was answered as fixed in an 8.1 update. If you have submitted other issues on this problem, please let me know how to find them (the ID number would be best.). In our problem tracking system, I find no open (or even recent) complaints about the build dependency system.

[Dishaw__Jim]

The only dependency issue that I have experienced, and it probably is how visual studio is designed, is that I have to designate the project dependencies via the "Project Dependencies" dialog. If I recall correctly I had to do that to get everything to compile and to link.

[Steven_L_Intel1]

Yes, if you have a solution with multiple projects, you do need to set the project dependencies. I don't think that was what Paul was referring to.

If there really is a problem, we'd like to know about it.