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

VS Studio and Intel Fortran RC1015 error message

RobertMcLean
Beginner
176 Views

I have a problem using Intel Fortran with Microsoft Visual Studio Community Edition.
I have read a series of posts here about this problem but I have not found a solution.

I get the error message "fatal error RC1015: cannot open include file 'winres.h' "
when I try to create a resource file, or design a form etc.

There is a post here from Bond_Andrew 08-02-2018


link to problem 

saying his problem was solved, it was due to the .rc extension being associated with Embarcadero's RADStudio at the time VS was installed. and he gives a link to the solution. But that link just leads to a list of posts that has nothing to do with the problem, I guess because there have been 7 years worth of posts in the mean time.

So I assumed that the answer is to correct the .rc extension association. I do use RADstudio so the solution sounded plausible to me. So I did that, changed it from bdslauncher to VS2022.

This did not solve the problem. So I noticed the phrase "at the time VS was installed".

So I did a fresh install of Visual Studio Community Edition, making certain .rc was not associated with Embarcadero. Then I did a fresh install of Intel fortran (intel-fortran-compiler-025.0.4.19_offline.exe ) and checked the boxes to integrate with VS 2022 and VS 2019.

No difference, still the same error message.

I have contacted VS help, and after a few emails back and forth, which basically told me to install Fortran again, and how to navigate through VS, they have now closed the ticket and said it is a Fortran problem not a Visual Studio problem, and gave me a link to here.

And I do have winres.h on my machine in several locations.

So, any suggestions ?
Is it possible to somehow find the answer that Bond_Andrew was speaking of in his 08-02-2018 post ?

Thank you, Robert

 

0 Kudos
0 Replies
Reply