|
3 | 3 | SOURCE Directory for the Tinker Package
|
4 | 4 | #######################################
|
5 | 5 |
|
6 |
| - This directory contains Fortran source code for the current |
7 |
| - version of the Tinker program package. |
| 6 | + This directory contains Fortran source code for the current version |
| 7 | + of the Tinker program package. |
8 | 8 |
|
9 |
| - The code is in a standard Fortran dialect that should compile |
10 |
| - unchanged on most machines. Script files to build the package |
11 |
| - on a variety of systems are in subdirectories named for the |
12 |
| - machine/operating system. A Makefile is also provided. |
| 9 | + The code is in standard Fortran and should compile unchanged on most |
| 10 | + systems. Script files to build the package on a variety of machines |
| 11 | + are in subdirectories named for machine/operating systems. Makefiles |
| 12 | + and scripts for use of cmake are also provided. |
13 | 13 |
|
14 |
| - Only a few source files may require editing prior to building: |
15 |
| - "sizes.f" which contains some master array dimensions used |
16 |
| - throughout the package, and "openend.f" which is a system |
17 |
| - dependent routine to open a file at the end. |
| 14 | + Only a few source files may require editing prior to building. These |
| 15 | + are "sizes.f" which contains master array dimensions used throughout |
| 16 | + the package, and "openend.f" which is a system dependent routine to |
| 17 | + open a file at the end. |
18 | 18 |
|
19 |
| - If you are building an OpenMP-capable version of Tinker with |
20 |
| - the Intel Fortran compiler, then it is necessary to uncomment |
21 |
| - the calls to Intel-specific extensions "kmp_set_stacksize_s" |
22 |
| - and "kmp_set_blocksize" near the top of the file "initial.f". |
| 19 | + If you are building an OpenMP-capable Tinker version with the Intel |
| 20 | + Fortran compiler, then it is necessary to uncomment the calls to |
| 21 | + Intel-specific routines "kmp_set_stacksize_s" and "kmp_set_blocksize" |
| 22 | + near the top of the file "initial.f". |
23 | 23 |
|
24 |
| - In addition, if your system does not support the iargc/getarg |
25 |
| - mechanism for command line arguments, then comment out the |
26 |
| - call to the subroutine "command" at the bottom of "initial.f". |
| 24 | + Also, if your system does not support the iargc/getarg mechanism |
| 25 | + for command line arguments, then comment the call to the subroutine |
| 26 | + "command" at the bottom of "initial.f". |
27 | 27 |
|
0 commit comments