Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29282 Discussions

Preferred compiler/linker options for distribution

Eric_L_3
Beginner
643 Views

What are the must haves to select in compiler and linker options for distribution of a console fortran exe. 

0 Kudos
2 Replies
Steven_L_Intel1
Employee
643 Views

First and foremost - a Release configuration, not Debug.

Other than that, as discussed in your other thread, you might choose to try to link to the static libraries. In general it would be preferable to keep using the DLL libraries but that means you have to install our redistributables along with your application. (You might also need the Microsoft Visual C++ redistributables.) I'll note that DLL linking is pretty much standard nowadays and reduces disk and memory load on the user's system. Also some language features are supported only in DLL libraries.

0 Kudos
Scott_L_
New Contributor I
643 Views

 

We recently converted from releasing MT-DLL builds to MT-static and have seen a smaller directory of static exe's than we had with dynamic  exe's and DLL's.  Also, we see the application starts up more quickly.   We certainly don't understand the difference.   It's been suggested virus scanning slows down the DLL's.  We have 20 ifort exe's and 9 ifort dll's.

 

scott

 

0 Kudos
Reply