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

libifcorert.dll & Path Revisited

Jugoslav_Dujic
Valued Contributor II
‎10-26-2005 12:54 PM
548 Views
What's the current state of the art in 9.0.024 regarding location of run-time libraries? I think I checked "Update environment variables" (but I might be wrong) but I don't see ...ia32lib directory appended to the path, nor I find libifcorert.dll on any other place.

As result, dynamically linked VF applications can not be freely executed from Explorer. If that's the typical setup for all users, I hesitate to distribute my applications as dynamically linked, because there's no guarantee they will run seamlessly.

I do know that MS introduced kind of Catch-22 situation in this field, but IVF setup should at least append ia32lib to Path environment variable (regardless of user's choice of "Update Environment Variables"), if no better option is available.

Jugoslav
0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎10-26-2005 01:28 PM
548 Views
Nothing has changed. Note that the DLLs are also in the BIN folder, which should have been added to the path.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.