Joined: 29 Nov 2006
|Posted: Sat Jun 25, 2005 3:45 am Post subject: Using ACML with the Salford FTN95 compiler
|Information privided by Michael Newark
No source file changes are necessary to call the ACML DLL from Ftn95. However, since Ftn95 uses a variant of the cdecl calling convention, the compiler has to be told that the routines in the DLLs are to be called using the CVF calling convention. This can be accomplished using the /IMPORT_LIB command line switch as follows:
ftn95 myprog /import_lib install_dirlibacml_dll.dll
where install_dir is the location of the DLL. The full pathname of install_dir should be specified to the DLL and should be enclosed within quotes if it contains spaces. The effect of this is to assume that all exported names in the DLL are CVF STDCALL and that any use of them should use the CVF STDCALL calling convention. External names passed via the argument list to a routine in the ACML DLL are automatically adjusted for whether or not they occur in the same source.
The ACML DLL library may be added to the Salford Slink command line as usual e.g
Slink myprog.obj install_dirlibacml_dll.dll
As with compilation, the full path to the DLL should be specified here, within quotes if the pathname contains spaces. It is worth emphasising that the linker should link directly against the DLLs not the *.lib files.