When you are using Visual Studio, you must create a project, which then resides in a "solution". Normally, when you create a new project, the solution is created automatically. A solution can hold more than one project and is something that builds an end result (executable, for example).
- Start Visual Studio 2019 and click "Create a new project".
- On the next screen, change the Language dropdown from "All languages" to Fortran.
- Change the project type dropdown from "All project types" to "Console". You can leave the Platform dropdown alone.
It will now look like this:
Since you have existing files, select Empty Project and click Next. The next screen will ask you to name the project and say where you want the new project/solution folder created. Click Create. On the new screen that appears, you'll see something like this on the right, reflecting your new project.
Now click Project > Add Existing Item... and select all your source files. Alternatively, you can use Project > Add Existing Items from Folder, or you can just "drag and drop" files onto "Source Files".
To build the project, select Build > Build Solution.
There is no built-in facility to create a makefile, though Visual Studio provides a tool called nmake.
To debug, you must first set a breakpoint at an executable statement (such as the first executable statement). If you don't do this, the debugger will just run to completion when you start debugging.
For more reading, see Using Microsoft Visual Studio* (intel.com)
Link Copied
When you are using Visual Studio, you must create a project, which then resides in a "solution". Normally, when you create a new project, the solution is created automatically. A solution can hold more than one project and is something that builds an end result (executable, for example).
- Start Visual Studio 2019 and click "Create a new project".
- On the next screen, change the Language dropdown from "All languages" to Fortran.
- Change the project type dropdown from "All project types" to "Console". You can leave the Platform dropdown alone.
It will now look like this:
Since you have existing files, select Empty Project and click Next. The next screen will ask you to name the project and say where you want the new project/solution folder created. Click Create. On the new screen that appears, you'll see something like this on the right, reflecting your new project.
Now click Project > Add Existing Item... and select all your source files. Alternatively, you can use Project > Add Existing Items from Folder, or you can just "drag and drop" files onto "Source Files".
To build the project, select Build > Build Solution.
There is no built-in facility to create a makefile, though Visual Studio provides a tool called nmake.
To debug, you must first set a breakpoint at an executable statement (such as the first executable statement). If you don't do this, the debugger will just run to completion when you start debugging.
For more reading, see Using Microsoft Visual Studio* (intel.com)
Visual Studio (on Windows) does not use gdb for debugging - it uses its own, excellent debugger. For Intel Fortran, the Microsoft debugger is enhanced with Fortran-specific support, but it is still the Microsoft debugger. IDB, which was at one time the Intel Debugger for Linux, no longer exists.
To build an application for debugging from the command line, add the /debug option to all commands. While it is possible to invoke the debugger from the command line, it is not a command line debugger (it's the Visual Studio debugger) and it is far easier to do this from within Visual Studio with the project you built there.
The compiler defaults for a new VS project are different from those on the command line. Especially for a Debug configuration, additional compile-time and run-time checks are enabled. You encountered one of these, generated interface checking. From the command line this is /warn:interface . Another option enabled in a Debug configuration is array and string bounds checking (/check:bounds).
As for Intel C++, the default is that you are using Microsoft Visual C++. You can right click on a C/C++ project and you will then see an "Intel Compiler" option:
If you select the Intel C++ Compiler Classic (I suggest not using the DPC compiler unless you are using its features), the project will be reconfigured, and it will show you the selected compiler after the project name:
If you want to revert to Visual C++, return to the Intel Compiler option in the project menu.
I loaded all of the Fortran code into a VS 2019 solution and compiled it.
The errors on a straight compile were
At the moment it is not going to run.
My suggestions:
1. if this is a class assignment for a masters or PhD class - find out the compiler from the professor where this last successfully compiled and hope you can find it. Ask for an exe files politely.
2. If this is your masters topic work then you need to fix all of the errors -- there are 20000 lines of code so someone with say 40 years of experience it will take a long weekend of nothing else -- you might just get it running - this includes getting rid of all of the commons, implicit variables and finding all of the missed named variables. The code was written in 1982 - there is a lot of potential errors that a modern compiler will pick up that the old compilers allowed. If you are doing it then set aside a month of time to learn and do it. At the end you will be a good programmer and intimately familiar with these people here. The six errors shown are just the tip of the iceberg, there are a lot there. Reading the code made me smile.
3. A modern compiler finds errors and ensures your code is more correct. As you update the more you find.
4. If you have to fix it - then you can start by asking on this forum what to fix first and we can go through the steps after you have read a book on Fortran. it is not difficult if you follow a path that is clear.
5. If this is your PhD work - develop new code from scratch using the Intel MKL libraries and some really fast solvers.
6. Understand this program was written by several people over 4 decades, you can see the problems. Try reading Beowulf in the original and you can understand the problems with the age of the code.
I would be honest with these people, what time do you have and how good does it have to be, and then you can work out a strategy that works.
Good luck.
