getting my build programs to make an *.exe file

[Markus54]

I was reading an article last night. It gave me instructions. Unfortunately, it does not provide a simpler way to make and executable file. Sometimes I can get an executable file and then when I click on the *.exe file I get an error.  I get the error libifcoremdd.dll cannot be found. Try re-installing. I did that. Now I am getting another message that a vcruntime is missing.

Yesterday I re=installed Visual Studio Community and all of Intel one API, including C++ and Fortran. I am looking forward writing Fortran AND Cobol code. So, my question is this, how do I find an easier way to convert an *.f90 file to a *.exe file and how do I fix these errors? 

OK, I just tried to put put a file here so you could see what I am talking about, but it didn't work.

Thanks,

Mark

[yzh_intel]

Hi, I think your runtime environment wasn't properly setup. In visual studio 2026, you can start the program via "Debug -> Start without debugging", maybe there's something similar in VS community.

[Markus54]

I have re-installed Visual Studio 2026 several times. I have 2 computers, an HP Laptop, a few months old. Then I have an older, more than 10 yrs old, desktop. It has Windows 10 on it. As far as my years of working with Windows and Unix goes everything installed in good fashion. 

Yes, I use the "Debug ->start without debugging. I want to see what my code is putting out .

Here is what I do: First, I write the Fortran code in VS. Then I click on debug, but when I can't see any of the errors. I have a 16" screen on my laptop. I debug, then build when the errors are gone. Then I build the solution. Then I go and find the *.exe and click on it. That is when I get the error for running the Fortran code. That's when I get the error of lib*.dll.

I tried to download 2022 VS pro. I ended up with 2026. I have things working except the executable run. So I am at a loss for these 2 things, making an executable file and getting rid of the errors when I click on the executable file.

[yzh_intel]

I think your experience shows where the problem is. When you do "Debug-> Start without Debugging", VS has set up the runtime environment for you. While when you click on the *.exe directly, probably the libraries you pointed out libifcoremdd.dll and vcruntime are somehow not in the environment PATH so they cannot be found.

You probably need to install oneapi compiler runtime, Get Runtime Versions of oneAPI Components  and also visual studio runtime. 

[Markus54]

OK, I clicked the link, but I haven't tried it yet.

[andrew_4619]

 libifcoremdd.dll is a debug lib. A Debug build exe can only be run within visual studio the debug libs are not part of the external environment. Are you trying to run the exe outside VS?

[Markus54]

I double-click on the file in file explorer. What I need to do is be able to write Fortran code, turn it into an *.exe to be used on another machine. Otherwise, what is the point of writing the code?

[Markus54]

I downloaded the runtime file, and now I can't run a program in file explorer. Also what order do I do the build solution and start debugging and start without debugging?

[Markus54]

OK, I also need to know how to shut off the aggravating suggestions that put words in my code that don't belong there. How can I get rid of suggestions in Visual Studio ?

[witwald]

@Markus54 In relation to the code completion niggle that you've mentioned, go to Tools | Options | Intellicode | General and try unchecking (switching off) the item "Automatically generate code completions in the Editor". Hopefully that will calm down your editor a little and keep those suggestions from intruding into your coding experience.

[Markus54]

Thanks, I will give this a try.

[Steve_Lionel]

To build a program that runs on other computers, build it as "Release Configuration". The other computer will need the Intel Fortran runtime installed, unless you change the Fortran project property Libraries to specify the static multithreaded (not debug) libraries.

[Markus54]

Thanks, I will give this a try tomorrow morning.