Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29274 Discussions

Keeping CVF and IVF-converted projects seperate

anthonyrichards
New Contributor III
‎08-08-2005 01:48 PM
402 Views
I am trialling the IVF 9.0 compiler. The CVF->IVF conversion/porting guide explains how to use the .DSW file as a starting point. Being a cautious soul, I wish to keep all my CVF projects 'as is' for the moment. When I convert from CVF workspace/projects to IVF Solutions, it would appear that I need to duplicate all my CVF projects (DSW's, project files etc.)and their associated Fortran files in new IVF 'solution' folders especially as the code will have to be converted to use different module names (IFWIN etc.). Or is there asafe efficient way of doing this that allows CVF projects and IVF solutions to co-exist in the same folders? Will the CVF .DSW and project files remain unaffected?

Message Edited by anthonyrichards on 08-08-2005 06:52 AM

0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎08-08-2005 02:24 PM
402 Views
No, you don't have to duplicate the files. If you want to keep using the CVF module names, you can. They still work. The conversion process does not affect the .DSW and .DSP files, though things might get confusing if both projects used the same Debug and Release folders.

If you find you have code that needs to know which compiler is being used, use !DEC$ IF DEFINED (__INTEL_COMPILER)
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.