Changes between Version 1 and Version 2 of FortranApps
- Timestamp:
- Apr 25, 2007, 12:01:49 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FortranApps
v1 v2 3 3 4 4 == F2X == 5 One option is to use f2c to convert your FORTRAN program to C. M.F. Somers has created a [http://boinc.gorlaeus.net/F2c.php BOINC-enabled f2c library] that simplifies this process. 5 One option is to use f2c to convert your FORTRAN program to C. M.F. Somers has created a [http://boinc.gorlaeus.net/F2c.php BOINC-enabled f2c library] that simplifies this process. 6 6 7 == Windows: cygwin == 7 Include the file 'boinc_api_fortran.C' in the api/Makefile.am, but comment out the 'zip' calls, to avoid the linking with 'libboinc_zip.a' 8 9 Include the file 'boinc_api_fortran.C' in the api/Makefile.am, but comment out the 'zip' calls, to avoid the linking with 'libboinc_zip.a' 8 10 9 11 To link it is necessary to include the 'winmm.dll' library (-lwinmm). 10 12 13 == Windows: Visual Studio == 11 14 12 == Windows: Visual Studio == 13 2004-06-16 note: this page is outdated; will update (functions are now declared `extern"C"` so no C++ mangling is done; there is a boinc_api_fortran.C wrapper) -- quarl@ssl 15 '''''2004-06-16 note: this page is outdated; will update (functions are now declared `extern "C"` so no C++ mangling is done; there is a boinc_api_fortran.C wrapper) -- quarl@ssl''''' 14 16 15 17 Note: a working example similar to the following (based on outdated BOINC code) is [http://boinc.berkeley.edu/TestLibs.zip here]; see also its [http://boinc.berkeley.edu/taufer.txt README]. 16 18 17 19 Start by creating a new FORTRAN project. Add all the FORTRAN specific files, then add all the files needed for the BOINC library (e.g. boinc_api.C). Make sure that BOINC and the FORTRAN files are compiled using the same type of standard libraries. i.e. if the BOINC is compiled with the debug multithreaded DLL libraries, make sure the FORTRAN files are compiled with the DLL setting. 18 20 19 21 For every BOINC function you want to call from fortran you must add an interface and subroutine: 20 21 22 22 23 {{{ … … 26 27 END INTERFACE 27 28 }}} 28 Remember to declare the type of arguments. INTEGER status 29 30 Remember to declare the type of arguments. INTEGER status 29 31 30 32 You must then tell the compiler that the function you are interfacing is a C routine. You do this by adding the statement: 31 32 33 33 34 {{{ 34 35 !DEC$ ATTRIBUTES C :: boinc_finish 35 36 }}} 36 Because BOINC is compiled as C++ files the FORTRAN compiler will not be able to find the standard function name in the object file, you therefore have to add an alias for the function giving the real function name: 37 38 Because BOINC is compiled as C++ files the FORTRAN compiler will not be able to find the standard function name in the object file, you therefore have to add an alias for the function giving the real function name: 39 37 40 {{{ 38 41 !DEC$ ATTRIBUTES ALIAS : '?boinc_finish@@YAHH@Z' :: boinc__finish 39 42 }}} 40 This function name can be found in the object file. Go to your compile directory and run dumpbin.41 43 44 This function name can be found in the object file. Go to your compile directory and run dumpbin. 42 45 43 46 {{{ 44 47 c:\fortranproject\Release>dumpbin /symbols boinc_api.obj 45 48 }}} 46 this will give you a list of symbols, where you can find the real functionname. The interface will end up looking like this: 47 49 this will give you a list of symbols, where you can find the real functionname. The interface will end up looking like this: 48 50 49 51 {{{ … … 55 57 END SUBROUTINE boinc_finish 56 58 END INTERFACE 59 }}} 57 60 58 }}} 59 You can now call the BOINC function in FORTRAN. 61 You can now call the BOINC function in FORTRAN. 62 60 63 {{{ 61 64 call boinc_finish(0)
