Unresolved External Symbol: WinMainCRTStartup

cstoyer · ‎01-21-2007

I am finally getting around to trying to teach this old dog some new tricks by moving from CVF and Visual Studioto IVF and Visual Studio.NET. I am using Winteracter and I did manage to getVS to find the library and include files for that. It is now under Tools/Options so I am hoping it will carry over from one project to another. In the CVF and Visual StudioI always had to add all this stuff into every new project and it was a PITA, to say the least.

I did a search on Winteracter and WinMainCRTStartup in this forum and did not find anything relevant.

I created the project by opening an existing CVF project.

I get the message that there is an unresolved external symbol: WinMainCRTStartup. As I understand, this is in the C library and it appears to me that the C library is in the library path. I contacted Winteracter Support(ISS) and they suggested the following:

"WinMainCRTStartup is the entry point for any Windows executable. It is provided by the C library. It calls WinMain which in turn, in a Winteracter program, calls your Fortran main program. The name of the C library containing the required function varies, depending on various factors, but will be one of libc.lib, libcmt.lib, etc. It is not advisable to link this explicitly. Rather you should normally allow IVF to choose the appropriate version. In any event, IVF should be linking with the C library automatically."

As far as I can tell, the path for the c libraries mentioned above are specified in the options.

I am using Winteracter v 6.10, which is compiled for IVF 8, but ISS says that should work for IVF 9.

The particulars for my installation are as follows:

Microsoft Visual Studio 2005

Version 8.0.50727.42 (RTM.050727-4200)

Microsoft .NET Framework

Version 2.0.50727

Installed Edition: Professional

Microsoft Visual C++ 2005 77626-009-0507763-41464

Microsoft Visual C++ 2005

Crystal Reports AAC60-G0CSA4B-V7000AY

Crystal Reports for Visual Studio 2005

Intel Fortran Compiler Integration

Intel Fortran Compiler Integration for Microsoft Visual Studio 2005,

Security Update for Microsoft Visual Studio 2005 Professional Edition -

ENU (KB925674)

This Security Update is for Microsoft Visual Studio 2005 Professional

Edition - ENU.

If you later install a more recent service pack, this Security Update

will be uninstalled automatically.

For more information, visit http://support.microsoft.com/kb/925674

Under Tools/Options and

Intel Fortran

General

Libraries:

$(IFORTInstallDir)Lib

$(VCInstallDir)lib

$(VCInstallDir)atlmfclib

$(VCInstallDir)atlmfclibi386

$(VCInstallDir)PlatformSDKlib

$(FrameworkSDKDir)lib

$(VSInstallDir)

$(VSInstallDir)lib

C:Program FilesMicrosoft Visual Studio 8VCATLMFCLIB

C:Program FilesMicrosoft Vi sual Studio 8VCLIB

C:Program FilesMicrosoft Visual Studio 8VCPlatformSDKlib

C:Program FilesMicrosoft Visual Studio 8SDKv2.0lib

c:wintlib.if8

It seems to indicate that the place where the libc and libcmt libraries are is being accessed (C:Program FilesMicrosoft Visual Studio 8VCLIB).

I realize there are some updates to the compiler and I will install them, but it seems this should get past where I am at with the original version.

However, I do seem to recall that the original Visual Studio.NET would not work with the IVF Fortran, but I am not sure if I received and installed an update for that.

OTOH, maybe this is the time to ditch Visual Studio and go to WiDE? It may be better in the long run? Is the debugging capability as good?

I am willing to supply any additional information you may need.

Thanks for any assitance.

Charles

Steven_L_Intel1 · ‎01-21-2007

Charles,

I'm going to take a wild guess here - while you indeed opened the CVF project and allowed it to be converted to a "Visual C++ project", you did not take the required second step of right clicking on the project in Visual Studio and selecting "Extract Compaq Visual Fortran Project Items". Try that.

If that isn't it, I can't tell what the problem is based on the information provded. Please file a support request with Intel Premier Support and attach a ZIP file of your project - we'll be glad to take a look. There's probably some odd project setting that is interfering.

I see no reason not to use the Visual Studio IDE - it's the only one with our Fortran debugging support.

John_N_2 · ‎07-31-2009

Quoting - Steve Lionel (Intel)

Charles,

I'm going to take a wild guess here - while you indeed opened the CVF project and allowed it to be converted to a "Visual C++ project", you did not take the required second step of right clicking on the project in Visual Studio and selecting "Extract Compaq Visual Fortran Project Items". Try that.

If that isn't it, I can't tell what the problem is based on the information provded. Please file a support request with Intel Premier Support and attach a ZIP file of your project - we'll be glad to take a look. There's probably some odd project setting that is interfering.

I see no reason not to use the Visual Studio IDE - it's the only one with our Fortran debugging support.

Steve:

Exactly what does Extract Compaq Stuff do?

John Nichols

Steven_L_Intel1 · ‎08-01-2009

Quoting - jm-nichols@tamu.edu1

Steve:

Exactly what does Extract Compaq Stuff do?

John Nichols

It reads the VC++ project that was converted from the VC6 form and pulls out the Fortran-specific build settings and source files, creating a Fortran project from it. Unlike with the VC6 environment of CVF, Visual Studio 2002 and later do not support a single project with mixed languages, hence the need for separate projects.