| View previous topic :: View next topic |
| Author |
Message |
saturn
Joined: 22 Apr 2008
Posts: 12
|
 Posted: Tue Apr 29, 2008 10:01 pm Post subject: Linking Intel Visual Fortran Object Files/DLLs in FTN95 |
 |
|
Has anyone got some experience in linking Intel Visual Fortran (IVF)
object files/ DLLs with SALFORD FTN95?
We have a transport model developed over the years using SALFORD
FORTRAN and recently decided to parallelise it to take advantage of
multi-core PC systems. The problem is that SALFORD does not support
OpenMP like IVF. Furthermore, we do not want to port the SALFORD source to IVF.
There are backward compatibility issues with user models that are
dependent on unformatted binary files and differences in Windows
programming.
The only option we’ve got is linking IVF object/DLL files in SALFORD,
which is proving to be a bit awkward. Does any have expertise in this area?
Last edited by saturn on Wed Nov 26, 2008 5:47 pm; edited 2 times in total |
|
| Back to top |
|
 |
PaulLaidler
Site Admin
Joined: 21 Feb 2005
Posts: 7926
Location: Salford, UK
|
| Posted: Tue Apr 29, 2008 10:17 pm Post subject: |
|
|
If the third party DLL uses the STDCALL protocol then you should try using /IMPORT_LIB <DLL name> on the FTN95 command line.
When using a Plato project, this can be done by selecting STDCALL in the Reference Properties Dialog when adding a Reference in the Project Explorer window.
Problems can occur when passing character strings because these require hidden arguments for the lengths of the strings and different compilers handle the hidden arguments in different ways. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
