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