Host software requirements for Intel Fotran

[amir_usa]

Hi everyone,

I am new to Intel Fotran and have recently downloaded the demo version for Windows (32bit). My question is if I purchase this compiler, do I still need to purchase MS Visual Studio? I have the old VC98 on my computer but the Intel fotran command line compiler still threw error 10036 (something about not finding VC++ directory).

I read the software requirements for Intel Fotran but couldn't understand it well. It says something like:

MS Visual Studio 2005 is optional for new purchases. For Evaluation, you must have MS Visual Studio.

I am trying to find out the requirements for compiling. Does the command line compiler requires MS C++ or is this something for IDE development?

[TimP]

This question was covered in exhaustive detail in an earlier thread:
http://software.intel.com/en-us/forums//topic/54272
Current purchased ifort includes Microsoft PPE, which includes the VS components needed for Fortran (but not C++) compilation, both command line and GUI.
32-bit ifort still works with VS 2003 (as well as 2005), but not with VS6.

[Steven_L_Intel1]

If you purchase a commercial or academic (not student) license for Intel Visual Fortran (and not as a "compiler suite" also including Intel C++), then there is nothing else to buy - the product works in the IDE and the command line. You can also use the product with Visual Studio 2005 if you already have that.

I know this can be confusing - how would you rewrite this to be more understandable?

[amir_usa]

Steve and Tim, thanks for your replies. I guess I should've done more searching in the threads about the requirements.

However, it is still not clear to me how to get the non-evaluation version. I am trying to buy on-line. I assume that after getting the evaluation version I would get a code to remove the 30 day restriction, or something like that. But how would I then get the VSPPE?

When I downloaded the evaluation version (without VS) I assumed that my old VC98 would suffice. Obviously this is not working. Also I can't really unserdtand why it is necessary to get VS for compiling and linking a simple executable with the command line compiler. It basically means the evaluation compiler wont do anything for you unless you get VS one way or another.

New addition

I fugured out how tobuy the non-evaluation version from the intel shop. Iguess that this includes the VSPPE.

I have just one more important question. I am working onuser subroutines for use with Abaqus on Windows and would likeeventually to run the fortran routine on Abaqus onthe Linux computer. Would I then need to purchase Intel Fotran for Linux? It would only be for linking with theuser subroutineusing Abaqus command line. Do I really need to get the full compiler for Linux as well?

[Steven_L_Intel1]

Amir,

When you purchase a regular license and register it, you're given access at the Intel Registration Center to a download that inckudes VSPPE. The evaluation download does not include VSPPE (and is thus 200MB smaller!)

The reason VS is needed is that we use Microsoft's linker and the MSVC libraries which we must license. You can get these for command line use free from MS, but MS will not let us include them with our compiler without paying a royalty. We can do that if you buy a license but not for a free evaluation copy. As MS' licensing model evolves, that may change in the future, but for now that's the way it is.

As for Linux, yes, you would need the Intel Fortran for Linux product to compile the source to the user routine and get the Linux libraries. Object and library files are not compatible between Windows and Linux.

[amir_usa]

Thanks for the info Steve. I already purchased the Windows edition and am using the compiler via the VSPPE. All is well so far.

As for the Linux issue, this is bad news. I would need to justify thiswith the project manager, especially that the Linux edition costs more than the Windows compiler. Abaqus on the Linux is much more faster than on Windows for our huge analyses and we are already paying a furtune for Abaqus :(