forums.silverfrost.com

[jlb]

When building a project containing only the following source file with the x64 Intel compiler called using Plato, the ClearWin64.lib library is always linked. Can this be avoided?

[mecej4]

The distribution of runtime library routines is different between 32- and 64-bit versions of Silverfrost Fortran. For your test program, the 64-bit versions of routines WSF1@@, CH@WSF and WSF2@ are in CLEARWIN64.dll. The corresponding 32-bit versions are in SALFLIBC.DLL

Type

[jlb]

mecej4

Thanks for that clarification. I understand this when I use the FTN95 compiler (32 and 64 bit), but not when I use the Intel iFort 64 bit compiler that is called from a Plato project.

[PaulLaidler]

jlb

Plato does include a reference to clearwin64.dll when compiling and linking using iFort and the reference is only needed for programs that use the ClearWin+ library.

The assumption is that programs that don't use ClearWin+ will use the iFort IDE or the command line in order to create release versions.

[PaulLaidler]

jlb

You could look at the file called BuildLog created by Plato when building an executable or DLL.

You could modify this to remove the reference to clearwin64.lib and make it into a batch file. You could run this batch file from a command line or create a macro in Plato in order to attach an accelerator key and run it that way.

[jlb]

Paul

Thank you for the detailed explanations. I had lost sight of the fact that the main purpose of using iFort and gfortran under Plato is to use Clearwin+. A short note in the help file about this assumption, which implies linking with the Clearwin64 library, might be useful for beginners like me.