If your application mixes Fortran with C or C++, you must configure Microsoft Visual Studio* to search Fortran include folders and libraries. This article describes the process for Microsoft Visual Studio 2017, 2015, 2013, 2012, 2010, 2008, 2005 and 2003, and applies to the following products:
This configuration needs to be done one time only per install of Microsoft Visual Studio.
Open Microsoft Visual Studio. Select Tools > Options. In the left pane, expand Projects and Solutions, click on VC++ Directories. (Visual Studio .NET 2003 uses "Projects" instead of "Projects and Solutions") and then select "Library Files" for "Show directories for".
Click on the New Line button (to the right of the "check mark" button) and enter the following new line if you are using Intel Visual Fortran XE 2011 or newer:
(remember to substitute for [vv] as described above)
or the following new line if you are using Intel Visual Fortran 11.x:
If you will be developing for the Intel 64 architecture, repeat the above steps, using the Platform dropdown to select "x64" (Intel 64) . When entering the path, use "intel64" instead of "ia32". Note that Microsoft Visual Studio 2003 does not support the x64 platform. If you do not see x64 as an available platform, see the Fortran Release Notes for instructions on how to configure Microsoft Visual Studio for 64-bit development.
If you are using Visual Studio 2005, you must install Visual Studio 2005 Service Pack 1, otherwise your Fortran project will not be found when linking the C/C++ project.
NOTE: In Microsoft Visual Studio 2010 and later, a C++ project will not link in a non-C++ dependent project library. If you are using a C/C++ main program with a Fortran static or dynamic library as a dependent project, you must explicitly provide the path to the Fortran library, (the .lib export library in the case of a DLL project), in the C/C++ project's Linker > Additional Dependencies property, or as a "source file" in the project. If your C++ project references ISO_Fortran_binding.h, also add libifcoremd.lib to Additional Dependencies.
NOTE: In Microsoft Visual Studio 2010 and later, a Fortran project will not link in a C++ DLL dependent project. A C++ static library dependent project will be linked in. If your Fortran project has a dependent C/C++ DLL project, you must explicitly provide the path to the C++ project's DLL export library (.lib) in the Fortran project's Linker > Additional Dependencies property, or as a "source file" in the project.
If you will be building Intel® 64 (x64) configurations:
Click on the Solution Explorer tab, or press Ctrl-Alt-L, to make it visible again.
If you do not see the Microsoft.Cpp.x64.user property page listed for the x64 configuration, right
click on Debug|x64 and select Add Existing property Sheet. Browse to the location which
contains the MsBuild 4.0 property pages. On Windows XP, this is typically:
C:\Documents and Settings\<username>\Local Settings\Application Data\Microsoft\MSBuild\v4.0
On Windows Vista* ,Windows 7* and later it is typically:
You may need to enable viewing of hidden files and folders to see these paths.
Microsoft.Cpp.x64.user.props and click Open. Now follow the steps above.
If you need further assistance with configuring Visual Studio to link with Fortran, please ask in our User Forum.
Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.
Notice revision #20110804