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.
29284 Discussions

How to create library with IVF 11?

DavidWhite
Valued Contributor II
551 Views

I use a third-party Windows front end called RealWin, which I build from various Fortran, C and assembler sources using a supplied batch file.

This batch file has the command below, which until now has worked with IVF 10, but fails under IVF11 (LIB is not a recognised command). It is intended to link the object files to create Realwin.lib. What do I need to do with IVF 11?

LIB realwin.obj winbase.obj rw_ctrl.obj rw_ctrl1.obj winmain.obj rwtoolxx.obj rw_dlg.obj clrabe.obj getmac.obj

Thanks,

David

0 Kudos
3 Replies
Steven_L_Intel1
Employee
551 Views

Should be the same. The problem you're having is that the Visual C++ "bin" folder is not on your PATH. How do you establish the command environment for this batch file?

0 Kudos
DavidWhite
Valued Contributor II
551 Views

Should be the same. The problem you're having is that the Visual C++ "bin" folder is not on your PATH. How do you establish the command environment for this batch file?

Steve,

I have not previously needed to make any changes to the environment after installing MSVS 2005 and IVF. Does this mean that upgrading to IVF 11 has changed some of the paths that were previously set?

I assume the folder you are refering to is

C:Program FilesMicrosoft Visual Studio 8VCbin

Thanks,

David

0 Kudos
Steven_L_Intel1
Employee
551 Views

David,

You need to start your command prompt session either by using the "Fortran Build Environment" shortcut the compiler installs or by having your script call ifortvars.bat. If you were simply relying on what was in the system PATH environment variable, then you will have to make adjustments to make sure ifortvars.bat is called (now with a "ia32" or "intel64" argument). This has been the case for a long time.

0 Kudos
Reply