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

Exporting makefiles (sort of)

ivfuser
Beginner
‎05-13-2005 05:01 AM
579 Views
I have recently made the switch to DevStudio .NET for the primary purpose of using IVF. So far, so good!

The docs for DevStudio .NET 2002 say that support for exporting makefiles has been eliminated. Swell. So much for easily diffing build configs.

The good news is, the new project files are not only human-readable, they seem to be readily parsable XML. Cool.

But wait. The IVF compiler and linker flags appear (Please correct me!) to be neither the short nor long forms of the CLI flags. Instead, the project files seem to be using nice descriptive names for the flags. That is welcome, especially if I have a mapping back to the CLI flags. Is this mapping documented?

Thanks
0 Kudos

Link Copied

2 Replies
Steven_L_Intel1
Employee
‎05-13-2005 12:34 PM
579 Views
No, it isn't. Sorry.
0 Kudos
Copy link
ivfuser
Beginner
‎05-13-2005 01:25 PM
579 Views
sblionel wrote:
No, it isn't. Sorry.



That's disappointing. I will log it with Premier Support.

Thanks.
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.