Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

Integration with Visual Studio

abhimodak
New Contributor I
‎02-13-2008 05:51 PM
588 Views
Hi

I want to use command line building with two different versions of the visual studio (viz. 2003 and 2005). However, when installing the compiler integrations we get to choose only one of the visual studio versions.

I can see the corresponding line in the appropriate IFORTVARS.bat file. For example, if I choose VS2005 then

Call "C:Program Files (x86)Microsoft Visual Studio 8VCBinVcvars32.bat".

Then to get command line building with VS2003 I thought I could just copy IFORTVARS.bat and change the above line to

Call "C:Program Files (x86)Microsoft Visual Studio .NET 2003Vc7BinVcvars32.bat"

I then created another shortcut and edited the new target to reflect new batch file.

However, I found that I can only compiler but not build an executable. The error message says that "mspdb80.dll" not found. Am I missing a step here?

I found that instead of deleting the original line I simply append the new line pointing to the other version of VS. Then, although the exe creation is successful, I get a message about the libcmt file.

Sincerely
Abhi

0 Kudos

Link Copied

2 Replies
Steven_L_Intel1
Employee
‎02-14-2008 06:01 AM
588 Views
You also need to edit ifort.cfg (same folder as ifortvars.bat) and remove the line starting with -Qlocation. The -Qvc8 in that file can be overridden with -Qvc7.1 in your command line when building with VS2003.
0 Kudos
Copy link
abhimodak
New Contributor I
‎02-14-2008 12:44 PM
588 Views
Thanks Steve.

Abhi
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.