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.
29298 Discussions

Combine Intel Fortran 2017 with Microsoft Visual Studio 11

Benedikt_R_
Beginner
‎12-04-2017 01:53 AM
688 Views

Dear list-members,

we use Intel Fortran 2017 on windows 10. The Fortran-code calls C-functions which were compiled with "Visual Studio 12".

We set the environment by calling "c:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2017.4.210\windows\bin\ipsxe-comp-vars.bat"

After additionally installing "Visual Studio 14" on the machine, the batch "ipsxe-comp-vars.bat" sets the environment for "Visual Studio 14" automatically.

We'd like to be able to control the used "Visual Studio"-Version: "ipsxe-comp-vars.bat" shall set up for "Visual Studio 12"

We are using Batch- and Makefiles only - no IDE.

Any advice?

Benedikt

0 Kudos

Link Copied

1 Reply
Steve_Lionel
Honored Contributor III
‎12-04-2017 05:53 AM
688 Views

The .bat file takes an optional argument of the name of the VS version you want to use, as long as it’s a supported version. For Parallel Studio 2017, you can use “VS2012” (no quotes) as that argument.

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.