Intel® Fortran Compiler 16.0 User and Reference Guide

Copying Projects

You need to follow certain procedures to move a project's location, whether you copy a project to:

If you upgrade your operating system version on your current system, you should delete the *.SUO and *.NCB files in each main project directory before you open solutions with the new operating system.

It is good practice to clean a solution before moving and copying project files. To do this, select Clean in the Build menu.

To copy an existing Intel® Fortran project to another disk or system:

  1. Copy all project files to the new location. You do not need to copy the subdirectories created for each configuration.

    Keep the directory hierarchy intact by copying the entire project tree to the new computer. For example, if a project resides in the folder \MyProjects\Projapp on one computer, you can copy the contents of that directory, and all subdirectories, to the \MyProjects\Projapp directory on another computer.

  2. Delete the following files from the main directory at the new location. These files are disk- and computer-specific and should not be retained:

    • *.SUO files

    • *.NCB files (if present)

  3. If you copied the subdirectories associated with each configuration (for example, Debug and Release ), delete the contents of subdirectories at the new location. The files contained in these subdirectories are disk- and computer-specific files and should not be retained. For example, Intel® Fortran module (.MOD) files contained in these subdirectories should be recreated by the compiler, especially if a newer version of Intel® Fortran has been installed.

    Note

    The internal structure of module files can change between Intel® Fortran releases.

    If you copied the project files to the same system or a system running the same platform and major Intel® Fortran version, do the following steps to remove most or all of the files in the configuration subdirectory:

    • Open the appropriate solution. In the File menu, either select Open Solution or select Recent Solutions. If you use Open Solution, select the appropriate .SLN file.

    • Select Set Active Configuration in the Build menu and select a configuration.

    • Select Clean in the Build menu.

    • Repeat the previous two steps for other configurations whose subdirectories have been copied.

  4. If possible, after copying a project, verify that you can open the project at its new location using the same Fortran version that it was created in. This ensures that the project has been moved successfully and minimizes the chance of conversion problems. If you open the project with a later version of Fortran, the project will be converted and you will not be able to convert the project back. For this reason, making an archive copy of the project files before you start is recommended.

  5. View the existing configurations. To view the existing configurations associated with the project, open the solution and view available configurations using the drop-down box at the top of the screen.

  6. Check and reset project options.

    Because not all settings are transportable across different disks and systems, you should verify your project settings on the new platform. To verify your project settings:

    1. From the Project menu, choose Properties. The Project Property Pages dialog box appears.

    2. Configure settings as desired. Pay special attention to the following items:

      • General: Review the directories for intermediate and output files. If you moved the project to a different system, be aware that any absolute directory paths (such as C:\TEMP or \Myproj\TEMP) will most likely need to be changed. Instead, use relative path directory names (without a leading back slash), such as Debug

      • Custom Build Step: Review for any custom commands that might change between platforms.

      • Pre-build, Pre-link, and Post-build Steps in Build Events: Review for any custom commands that may have changed.

  7. Check your source code for directory paths referenced in INCLUDE or similar statements. Visual Studio* provides a multi-file search capability called Find in Files, available from the Edit menu.