rc.exe not found error during build

[Ron_F_1]

I just installed the Parallel Studio XE composer Edition for Fortran Windows.  Now when I try to rebuild executables that I developed using an earlier Intel compiler, I get the errors:

rc.exe not found

and

error code 23 (returned by OPenValidat X) opening pdb Debug\ vc140.pdb

How do I resolve this?

Thanks

[Kevin_D_Intel]

Sorry to hear about the issues. We need some specifics about the versions of Parallel Studio XE and Microsoft Visual Studio you have.

Did you install the Parallel Studio XE 2016 release?  Or an earlier version?

What version of Visual Studio are you using?   Are you using any version of the VS Shell?

I don't know whether this earlier reply from Steve about rc.exe might be applicable/helpful for your case, https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/539486#comment-1832785

The error code 23 issue appears to be a known issue, https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/591188, which appears you could safely ignore at this time.

[Ron_F_1]

Yes, I installed the Parallel Studio XE 2016 release.  I also installed Visual Studio 2015 before I installed the Parallel Studio.

I'm not sure about a VS Shell, I only installed VS 2015.  Thanks for your help. 

[Kevin_D_Intel]

Sounds like you installed a full Visual Studio 2015 version and not the VS Shell included with our product and that's just fine.

Just to cover one other base. When you installed VS 2015, did you specifically install the Visual C++ support?    (That's discussed here, https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/590621)

On my system, rc.exe is located at:

C:\Program Files (x86)\Windows Kits\8.1\bin\x86    -and-      C:\Program Files (x86)\Windows Kits\8.1\bin\x64

It is my understanding this Windows 8.1 kit should install as part of the Visual Studio 2015.

[Ron_F_1]

Kevin,

It looks like I installed the Community version of Visual Studio 2015.  I would really just prefer to use the VS Shell that is included with the Intel Fortran Compiler.  Would that be easy to do?

I'm pretty sure I did install the Visual C++ support before.  I looked at the locations that you suggested for the rc.exe file, but did not see it there.

Thanks

Ron

[TimP]

When I "upgraded" VS2015 to a current version which has that install menu, the Windows Kits\8.1 dropped off the environment variables, although it is still present on disk.  Is that part of the problem?

When working with ifort, everything seems OK until it fails to link kernel32.  When working in C++ STL, there are undefined macros from includes, but either CL or ICL can make a .obj when there is no STL requirement.

Each new version of VS2015 has taken me further from working, but VS2013u5 is fine. 

If you install without accepting integration into any version of Visual Studio which it may find, it should go into the path of telling you if you need Windows Kits\8.1\ etc. to support the VS2013 Shell.  I don't know if there's any advantage in Shell over a full VS2013.

[Kevin_D_Intel]

Hi Ron,

Community version should also work. I’m unsure why rc.exe seems to be missing in your case. Since you prefer using the VS 2013 Shell provided with our product then I recommend starting over.

First, uninstall our product and then uninstall the VS 2015 Community. It may be necessary to manually delete the Visual Studio 14.0 directory from under Program Files and/or Program Files (x86) after following the uninstallation.

Next, to use the VS 2013 Shell included in our product, you must first install the Microsoft Windows SDK for Windows 8.1. Refer to Install Windows SDK for VS2013 Shell for more details and link to obtain that from Microsoft.

After installing the Windows SDK, start the installation of our product and follow the prompts. Our installation should detect that no installed Visual Studio version and present a Pre-requisite summary about using Visual Studio 2013 Shell. With the Windows SDK installed, proceed with the installation which should install our product and the VS 2013 Shell.

Keep us posted.

@Tim – My understanding is the decision to use the VS Shell occurs earlier in the installation flow than where integration with specific versions is decided/chosen.

[Ron_F_1]

Kevin,

I removed and reinstalled as you suggested, and am now able to compile a small code that I have successfully. 

However when I try to compile a large code (that I can compile on the 2011 Intel Fortran compiler), I get a lot of errors of the type:

error #6633: The type of the actual argument differs from the type of the dummy argument.

Do you know how I can avoid that?  This code runs fine with this source code.

Thanks,

Ron

[Kevin_D_Intel]

Glad to hear you are over that hurdle.

As for avoidance of the error, that requires inspection of the related source if you can share that.  Can you share the affected call and the arguments along with their declarations, any related interface declaration, the callee and the dummy argument declarations to start with?

If you cannot share any source publically in this forum then you can attach that in a private reply (Send Author A Message) to me and we can inspect those and advise you on what's needed.

[Ron_F_1]

Kevin,

I went back and did a rebuild of all the files, and it compiled and linked fine, so I think it was related to having some of the project files compiled with the old Intel compiler, and others with the new one.

Thanks for your help,

Ron

[Kevin_D_Intel]

Glad to hear that!