https://community.intel.com/t5/Software-Archive/Conversion-to-DLL/m-p/986142#M27148 Currently I have a standalone Visual Fortran application that is linked against a large number of static libraries and includes a block data common. I need to convert it to a DLL, which will be called from Visual Basic front end. I know how to do the VB/VF part since I have done a number of simple examples with simple VF DLL's. <BR /> <BR />In the old FAQ I read the following: <BR /> <BR />?Can I build a VF DLL that is linked against the VF static libraries? 29-Oct-1997 <BR /> <BR />We strongly recommend that you NOT do this as it can cause subtle and difficult to analyze application errors. If you build a DLL, always link against the shared libraries. Furthermore, any application linked against your DLL must be linked against DLL, not static libraries.? <BR /> <BR />My question is: what would be the most straight forward way to do what I need to do? Do I need to convert each of the static libraries into a DLL (each library contains multiple subroutines)? Alternatively, can I just convert my top-level routine into a DLL and still keep it linked against the static libraries not withstanding what 10/29/97 FAQ recommends? <BR /> <BR />Any suggestions will be greatly appreciated. <BR /> <BR />Maria Fri, 15 Mar 2002 05:28:29 GMT maria14 2002-03-15T05:28:29Z https://community.intel.com/t5/Software-Archive/Conversion-to-DLL/m-p/986142#M27148 Currently I have a standalone Visual Fortran application that is linked against a large number of static libraries and includes a block data common. I need to convert it to a DLL, which will be called from Visual Basic front end. I know how to do the VB/VF part since I have done a number of simple examples with simple VF DLL's. <BR /> <BR />In the old FAQ I read the following: <BR /> <BR />?Can I build a VF DLL that is linked against the VF static libraries? 29-Oct-1997 <BR /> <BR />We strongly recommend that you NOT do this as it can cause subtle and difficult to analyze application errors. If you build a DLL, always link against the shared libraries. Furthermore, any application linked against your DLL must be linked against DLL, not static libraries.? <BR /> <BR />My question is: what would be the most straight forward way to do what I need to do? Do I need to convert each of the static libraries into a DLL (each library contains multiple subroutines)? Alternatively, can I just convert my top-level routine into a DLL and still keep it linked against the static libraries not withstanding what 10/29/97 FAQ recommends? <BR /> <BR />Any suggestions will be greatly appreciated. <BR /> <BR />Maria Fri, 15 Mar 2002 05:28:29 GMT https://community.intel.com/t5/Software-Archive/Conversion-to-DLL/m-p/986142#M27148 maria14 2002-03-15T05:28:29Z https://community.intel.com/t5/Software-Archive/Conversion-to-DLL/m-p/986143#M27149 No, that FAQ has nothing to do with your case -- it refers to VF run-time libraries (DFORRT.dll/DFORRT.lib). You can safely link your own static libraries wherever you want. Sat, 16 Mar 2002 02:12:04 GMT https://community.intel.com/t5/Software-Archive/Conversion-to-DLL/m-p/986143#M27149 Jugoslav_Dujic 2002-03-16T02:12:04Z