topic Re: Distributing run-time libraries in Software Archive

Distributing run-time libraries

Intel_C_Intel — Sat, 21 Apr 2001 01:43:17 GMT

I checked the FAQ's and Knowledge Base, and didn't see an answer. Two quick questions:

1. I need to provide documentation regarding the legal implications of distributing the run-time libraries (DFORRT.DLL, DFORRM.DLL, etc.) with our DLL. As I understand it, if we have a license, we may distribute legally without royalty compensation, is this true?

2. Is there anyway to package the necessary run-time library inside the dll we are distributing? (I suspect not, but I need confirmation)

Thanks,
dfh

Re: Distributing run-time libraries

Steven_L_Intel1 — Sat, 21 Apr 2001 02:03:37 GMT

This is spelled out in your license agreement.

You can distribute our dlls along with yours - I do not recommend linking in a static version of the run-time library unless you know for certain that no other Fortran code will be used in the application. Note that you probably need only one of DFORRT.DLL and DFORMD.DLL - the latter is if you build against the threaded libraries.

Steve

Re: Distributing run-time libraries

isn-removed200637 — Mon, 23 Apr 2001 16:19:14 GMT

To DFH, Just a thought: If you use QuickWin help, don't forget to include FQWIN.HLP also, or else extract the QuickWIn help topics from it (using HCW.EXE) and include them in your own help
file.

A question for Steve: with the exception of the help file noted above, under what circumstances could a statically-linked executable still require
access to other VF routines not included at the link stage?

Re: Distributing run-time libraries

Steven_L_Intel1 — Mon, 23 Apr 2001 22:39:31 GMT

Anthony,

If an application uses the modeless dialog support in DFLOGM, it needs DFDLG100.DLL, but otherwise, I can't think of any other Fortran components needed by a statically linked application.

Steve