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

Intel Visual Fortran 11.1.060 Ignoring Additional Include Directories

chauvjo
Novice
‎03-02-2010 12:04 PM
330 Views

I am using the Intel Visual Fortran 11.1.060 and Visual Studio 2008 and cannot get the compiler to find my include files even when I provide the pathname under Fortran -> Preprocessor -> Additional Incude Directores. The include files are in a different directory than the source files. Here is what is shown under Fortran -> Command Line window.

/nologo /debug:full /Od /I"C:\\Documents and Settings\\chauvjo\\Desktop\\Tools Work\\Misan\\Misan_02272010\\Window" /I"s\\Intel Visual Fortran\\Compiler Release 11.1.060\\32-bit\\Include\\\\" /gen-interfaces /extend_source:132 /warn:interfaces /Qsave /Qzero /module:"Debug\\\\" /object:"Debug\\\\" /traceback /check:bounds /libs:static /threads /dbglibs /c

It appears that the compiler is splitting the pathname for some reason. Here is the actual pathname:

C:\\Documents and Settings\\chauvjo\\Desktop\\Tools Work\\Misan\\Misan_02272010\\Windows\\Intel Visual Fortran\\Compiler Release 11.1.060\\32-bit\\Include

Any ideas?

0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎03-02-2010 01:56 PM
330 Views
Please attach your .vfproj file - that's all I need to see. I tried to reproduce this but could not.
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.