| 20 | | element generator. |
| | 20 | element generator. Details and links for the compilers can be found |
| | 21 | [http://projects.hepforge.org/whizard/compilers.html here.] |
| | 22 | |
| | 23 | After you downloaded the most recent tarball from the main page, |
| | 24 | unpack it, go to the WHIZARD directory, create a new {{{build}}} |
| | 25 | directory and go there. In that directory, perform a |
| | 26 | {{{../configure FC=<your FORTRAN compiler> --prefix=/usr/local}}}. |
| | 27 | Note that this is because the source and compile directories should be |
| | 28 | different to avoid any problems during compilation and |
| | 29 | installation. {{{../configure --help}}} shows you the options for the |
| | 30 | configure process you have. The {{{FC}}} environment variable |
| | 31 | allows you to specify your FORTRAN compiler of choice. Note that |
| | 32 | WHIZARD 2 has been written in Fortran 2003 in a fully |
| | 33 | object-oriented way. We highly recommend usage of the standard |
| | 34 | {{{gfortran}}} compiler from version 4.5.0 on. You can access the |
| | 35 | help menu of configure by {{{../configure --help}}}. |
| | 36 | {{{./configure -V}}} shows you the actual version of |
| | 37 | your downloaded WHIZARD distribution. The possible environment |
| | 38 | variables are: |
| | 39 | |
| | 40 | {{{ |
| | 41 | CC C compiler command |
| | 42 | CFLAGS C compiler flags |
| | 43 | LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a |
| | 44 | nonstandard directory <lib dir> |
| | 45 | LIBS libraries to pass to the linker, e.g. -l<library> |
| | 46 | CPPFLAGS C/C++/Objective C preprocessor flags, e.g. -I<include dir> if |
| | 47 | you have headers in a nonstandard directory <include dir> |
| | 48 | CPP C preprocessor |
| | 49 | FC Fortran compiler command |
| | 50 | FCFLAGS Fortran compiler flags |
| | 51 | CXX C++ compiler command |
| | 52 | CXXFLAGS C++ compiler flags |
| | 53 | CXXCPP C++ preprocessor |
| | 54 | }}} |
| | 55 | |
