- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've noticed that an IVF 8 project linked to IMSL doesn't seem to have any IVF RT dependency.
Also, a CVF project converted to IVF via the wizard and ifort /nologo /iface:cvf /iface:mixed_str_len_arg 'ed has a RT dependency on DFORRT.DLL but no apparent IVF dependency.
What are the names of typical IVF RT dependencies?
Thanks,
Gerry T.
Also, a CVF project converted to IVF via the wizard and ifort /nologo /iface:cvf /iface:mixed_str_len_arg 'ed has a RT dependency on DFORRT.DLL but no apparent IVF dependency.
What are the names of typical IVF RT dependencies?
Thanks,
Gerry T.
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The default is static linking, so there would be no DLL dependencies. If you have a CVF project converted that is dependent on DFORRT.DLL, you did not rebiuild it in Intel Fortran.
The IVF equivalent of DFORRT.DLL is IFCORERT.DLL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, of course, static linking is the desault.
The former CVF project was rebuilt as an IVF project and the DFORRT.DLL dependency remained. It turns out that the IVF app calls the MATLAB R12 engine and it's it that has the DFORRT.DLL dependence. I'd say that MATLAB R13 has an IFCORERT.DLL dependence.
Thanks,
Gerry T.
The former CVF project was rebuilt as an IVF project and the DFORRT.DLL dependency remained. It turns out that the IVF app calls the MATLAB R12 engine and it's it that has the DFORRT.DLL dependence. I'd say that MATLAB R13 has an IFCORERT.DLL dependence.
Thanks,
Gerry T.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I ran into this same problem, but did not have it in a different project. Both projects were built with the /lib:static setting (in Visual Studio, go to Project Settings/Fortran tab/Libraries category, select single threaded in the run-time library box.) Project A also checked the "use IMSL math library" under other library options. ProjectA then refers to DFORRT.DLL for some reason, in spite of the/lib:static setting.(dumpbin lists DFORRT.DLL as an import). Project B did not check the "use IMSL math library" option, but instead got the IMSL library by going to the Link tab in the Settings window and adding smathd.lib to the object/librarybox. This DLL does not import DFORRT.DLL.
When I went back to project A and unchecked the "use IMSL math library" box and added smathd.lib to the link step, project A no longer used DFORRT.DLL.
I don't understand why this happens, but it does and the above steps work around it.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page