The distribution of MOPAC2009 source is restricted to sites that have signed an End User License Agreement. After the EULA has been received at SCC, source will be sent electronically to the site. Please indicate which of the two platforms, WINDOWS or Linux, that you want to compile MOPAC2007 on.
All the files are in seven folders:
| Folder | Contents | |
| MOPAC | mopac.f90, to_screen.f90, jdate.f90, a Makefile, and CVF build files for MOPAC2007 | |
| Subroutines | CVF build files for compiling all the subroutines | |
| src_subroutines | Source code for all the subroutines | |
| Modules | CVF build files for compiling all the modules | |
| src_modules | Source code for all the modules (These files end in "_C.f90") | |
| Interfaces | CVF build files for compiling all the interfaces | |
| src_interfaces | Source code for all the interfaces(These files end in "_I.f90") |
The development compiler used at SCC is Compaq Visual Fortran, and the following instructions assume that CVF is being used. If you are using a different compiler, then use the instructions as a guide.
The dependencies are as follows:
To compile, open the CVF window, and compile using build => build MOPAC2009.exe. This will put the Release executable in M:/utility. If you want it to go somewhere else, change the entry in Project => settings => Link => Output file name.
First, copy all the files in directories src_subroutines, src_modules, and src_interfaces into the directory MOPAC. The original directory structure was intended for use on a WINDOWS platform, and the use of separate directories was convenient there. On Linux platforms, the Makefile utility does not need separate directories for each group of source files.
Read over the Makefile, and make any changes necessary. The most probable change would be to replace the FORTRAN compiler, "g95" with a different compiler.
When the command, "make MOPAC2009.out" is issued from within the directory MOPAC, the Makefile will build MOPAC2009.out.