cannam@167: Next: Linking and Initializing MPI FFTW, Previous: Distributed-memory FFTW with MPI, Up: Distributed-memory FFTW with MPI [Contents][Index]
cannam@167:All of the FFTW MPI code is located in the mpi subdirectory of
cannam@167: the FFTW package. On Unix systems, the FFTW MPI libraries and header
cannam@167: files are automatically configured, compiled, and installed along with
cannam@167: the uniprocessor FFTW libraries simply by including
cannam@167: --enable-mpi in the flags to the configure script
cannam@167: (see Installation on Unix).
cannam@167:
cannam@167:
Any implementation of the MPI standard, version 1 or later, should
cannam@167: work with FFTW. The configure script will attempt to
cannam@167: automatically detect how to compile and link code using your MPI
cannam@167: implementation. In some cases, especially if you have multiple
cannam@167: different MPI implementations installed or have an unusual MPI
cannam@167: software package, you may need to provide this information explicitly.
cannam@167:
Most commonly, one compiles MPI code by invoking a special compiler
cannam@167: command, typically mpicc for C code. The configure
cannam@167: script knows the most common names for this command, but you can
cannam@167: specify the MPI compilation command explicitly by setting the
cannam@167: MPICC variable, as in ‘./configure MPICC=mpicc ...’.
cannam@167:
cannam@167:
If, instead of a special compiler command, you need to link a certain
cannam@167: library, you can specify the link command via the MPILIBS
cannam@167: variable, as in ‘./configure MPILIBS=-lmpi ...’. Note that if
cannam@167: your MPI library is installed in a non-standard location (one the
cannam@167: compiler does not know about by default), you may also have to specify
cannam@167: the location of the library and header files via LDFLAGS and
cannam@167: CPPFLAGS variables, respectively, as in ‘./configure
cannam@167: LDFLAGS=-L/path/to/mpi/libs CPPFLAGS=-I/path/to/mpi/include ...’.
cannam@167: