- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Lee
Link Copied
- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That worked great!
Place the IMSL lib and include folders within Tools .. Options .. Intel Fortran .. General. Then, you don't need to do it at the project level. .NET remembers it for all projects.
Lee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ciao,
Gerry T.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the help. I'm getting close to getting it to work.
I am creating a dll. If I select Configuration Properties / Fortran / LIbraries / Runtime Library as Debug Single-threaded, then I am able to debug the dll using an Excel spreadsheet and VBA. If I select the Debug Single-threaded DLL option, then the VBA code fails with error 53 - dll file not found.
Does the first option use the static fortran library and the second option use the run-time fortran dll? What is the name of the run-time dll?
Thanks,
Lee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've made progress on getting the Single-threaded DLL to run. I switched from a spreadsheet to a C# console application for the call to the DLL. .NET gave much better messages of the error when trying to run the DLL. The following threeDLLs were not found:
libifcorertd.dll libmmd.dll libmmdd.dll
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Those files should be present in every installation of ifort 8.0, standard location program filesintelfortrancompiler80ia32lib
You would not be able to build any Fortran application if your VS is not set up to use that folder.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, I found the files and copied them to C:WindowsSystem32 as a temporary fix to get it working. What is the proper solution for the IDE to find them?
Thanks,
Lee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As mentioned above, you don't have to copy the files anywhere. Just make sure that the folder they're in is included in the list that is the value of the PATH environment variable. That's the way the compiler install sets it up if you specify that environment variables are to be updated.
It's sort of a mess - Microsoft's rules for Windows Installer disallow a product from copying DLLs into Windows or Windows System - the idea being that you put the DLLs along side the EXE. But that doesn't work for things such as compilers, where the user creates the EXE. And of course Microsoft flouts its own rule by putting its own language DLLs in Windows System. Putting the folder in PATH is the recommended approach.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did I miss something on installing the software that the PATH was not updated for being able to run programs from the IDE?
Thanks,
Lee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »