Using Intel and Compaq Fortran with same code (not at same time!)

[nameiii]

We are about to convert to Intel Fortran (with Visual Studio .NET 2003) from Compaq (6.6) - about time too I hear you say! But I would like to keep the option, for a while at least,of compiling with either compiler.

When using the Intel project conversion wizard, there is a warning message along the lines of "you will not be able to edit this project in previous versions of Visual Studio". This doesn't say anything about "Developer studio" as used by Compaq Fortran and in practice it seems to be OK - it looks like the studio files (.sln, .dsw etc) are disjoint between the two systems. Can anyone confirm that this is the case and that it is safe to use the two compilers with the associated studios in parallel for different builds on the same project?

Many thanks

[ZlamalJakub]

I am using the same fortran sources in Intel and CVF compiler (but copied in different directories).

Problem can occur in compiled *.obj and *.mod files, because they are not compatible.

If You ensure that CVF will compile all sources to let say CVF/Debug and IVF to IVF/Debug subdirectories it should work correctly together.

Jakub

[Steven_L_Intel1 · Accepted solution]

The warning is telling you that changes you make in the Intel Fortran project settings will not be visible in CVF and vice-versa. As noted, make sure that the output directories are distinct. You can, of course, have entirely separate project directory trees and add sources from a common location - there's no requirement that sources be contained within the project/solution directory tree.

[lklawrie]

I too have both CVF and IVF on my computer and running our codes on both. Which means we limit the number of 2003 items we can put into CVF. Sometimes I have written "CVF only" routines to supplement. (I also have g95 as a test compiler).

I'd suggest you don't do the project conversion wizard and start from scratch with IVF in a different folder.

Linda

[nameiii]

Many thanks to all three responses to my question. I now know exactly what to do.