libpsht Code
Brought to you by:
reinecke
File | Date | Author | Commit |
---|---|---|---|
c_utils | 2012-07-17 | reinecke | [r20] documentation update |
config | 2012-02-24 | reinecke | [r17] small updates to the FFT routines, documentatio... |
docsrc | 2011-02-04 | reinecke | [r10] - add MPI support |
libfftpack | 2012-02-24 | reinecke | [r17] small updates to the FFT routines, documentatio... |
libpsht | 2012-11-16 | reinecke | [r22] adopt GSL function for Gauss-Legendre quadrature |
COPYING | 2010-11-16 | reinecke | [r1] initial import |
Makefile | 2011-07-08 | reinecke | [r14] add autoconf support |
README.compilation | 2012-02-24 | reinecke | [r17] small updates to the FFT routines, documentatio... |
configure.ac | 2012-11-16 | reinecke | [r22] adopt GSL function for Gauss-Legendre quadrature |
make_release | 2012-02-24 | reinecke | [r18] add make_release script |
GNU make is required for compilation. There are now two ways to compile libpsht: using the configure script (recommended) or the traditional manual approach. 1) Using configure Simply run "./configure"; if this fails, please refer to the output of "./configure --help" for additional hints and, if necessary, provide additional flags to the configure script. Once the script finishes successfully, run "make" (or "gmake"). This should install the compilation products in the subdirectory "auto/". 2) Manual setup To compile the package, set the environment variable PSHT_TARGET to the target for which you want to compile (e.g. generic_gcc, linux_icc etc.). If a fairly recent version (4.2 or higher) of gcc is installed on the system, the target "generic_gcc" should always work (except for Mac OSX where "osx_gcc" should be used). For each possible target there exists a configuration file with the name config.$PSHT_TARGET in the directory config/. Afterwards, just type "gmake" or "make". If the compiler on your platform has a different name or you want to make other changes, editing the configuration files should be quite straightforward. Please note that all temporary and object files are created separately from the source files in a directory called "build.$PSHT_TARGET". This allows simultaneous compilation for different platforms. Documentation can be created by the command "(g)make doc". However this requires the doxygen application to be installed on your system. The documentation will be created in the subdirectory doc/.