Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.

XEffort library issues

DavidWhite
Valued Contributor II
2,631 Views

I have been using XEffort for some years, and without making any changes to my code or to the libraries, since updating to the latest SP1 of XE Studio, I am now seeing a range of errors which have me mystified.

1. I have been using USE XFTSTrings,only : XToUpper, XEnvironmentString

Now, this won't link, and I need to USE XFTFile to get XEnvironmentString

2. My main program will no longer link, as I am getting an unresolved external _XINIT in WinMain@16 (my XINIT subroutine is still in the source and is compiling, but is not found at link time).

What has changed to cause these errors, particularly 2? My source code and source libraries have not been changed.

Thanks,

David

0 Kudos
25 Replies
Neels
New Contributor II
452 Views

Steve Lionel (Intel) wrote:

The problem here is the use of _DF_VERSION, which we no longer define. We use __INTEL_COMPILER. You could add /D_DF_VERSION=650 to your compiles and it should work. As for keeping a copy of Xeffort, is Jugoslav Dujic no longer maintaining his site for that?

Steve,

I have just updated to "Intel(R) Visual Fortran Compiler XE 14.0.3.202 [IA-32]" and I am getting the same "WinMain@16" error. I have added the "/D_DF_VERSION=650" in the command line option but it does not solve the issue. Any suggestions?

I rebuild both Xeffort and my project.

"error LNK2019: unresolved external symbol _XINIT referenced in function _WinMain@16    Xeffort.lib(EXWinMain.obj)    "

Neels

0 Kudos
Steven_L_Intel1
Employee
452 Views

Neels, I think that's a separate issue. That suggests your program is not structured as a "Windowing application" with a WinMain entry point.

0 Kudos
Neels
New Contributor II
452 Views

Steve,

It is a dialog based application created using the Xeffort wizard. It worked fine in CVF and IVF up to XE 13.--- but not in XE14.---. Other than that I have no idea.

Neels

0 Kudos
DavidWhite
Valued Contributor II
452 Views

Neels,

In my applications (not tested in XE 14), I do not use any command line options like yours, but in my source for XINIT have removed all refereces to DF:

LOGICAL FUNCTION XInit(szCmdLine,nCmdShow)

!DEC$ATTRIBUTES DEFAULT, DECORATE, ALIAS: 'XINIT':: XInit

Not sure if this is helpful.

David

0 Kudos
Neels
New Contributor II
452 Views
Thanks David, After reading Steve's comment I had a look at the XInit function and realized it still has the !IF statement in that tested for he old compiler version. Commenting all out except the line you show solved the issue. A case where knowing the answer made me understand the advice given. neels
0 Kudos
Reply