- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
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
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
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

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page