Chris@19: Chris@19: Chris@19: Installation on Unix - FFTW 3.3.4 Chris@19: Chris@19: Chris@19: Chris@19: Chris@19: Chris@19: Chris@19: Chris@19: Chris@19: Chris@19: Chris@19: Chris@19: Chris@19: Chris@19:
Chris@19: Chris@19:

Chris@19: Next: , Chris@19: Previous: Installation and Customization, Chris@19: Up: Installation and Customization Chris@19:


Chris@19:
Chris@19: Chris@19:

10.1 Installation on Unix

Chris@19: Chris@19:

FFTW comes with a configure program in the GNU style. Chris@19: Installation can be as simple as: Chris@19: Chris@19:

     ./configure
Chris@19:      make
Chris@19:      make install
Chris@19: 
Chris@19:

This will build the uniprocessor complex and real transform libraries Chris@19: along with the test programs. (We recommend that you use GNU Chris@19: make if it is available; on some systems it is called Chris@19: gmake.) The “make install” command installs the fftw Chris@19: and rfftw libraries in standard places, and typically requires root Chris@19: privileges (unless you specify a different install directory with the Chris@19: --prefix flag to configure). You can also type Chris@19: “make check” to put the FFTW test programs through their paces. Chris@19: If you have problems during configuration or compilation, you may want Chris@19: to run “make distclean” before trying again; this ensures that Chris@19: you don't have any stale files left over from previous compilation Chris@19: attempts. Chris@19: Chris@19:

The configure script chooses the gcc compiler by default, Chris@19: if it is available; you can select some other compiler with: Chris@19:

     ./configure CC="<the name of your C compiler>"
Chris@19: 
Chris@19:

The configure script knows good CFLAGS (C compiler flags) Chris@19: for a few systems. If your system is not known, the configure Chris@19: script will print out a warning. In this case, you should re-configure Chris@19: FFTW with the command Chris@19:

     ./configure CFLAGS="<write your CFLAGS here>"
Chris@19: 
Chris@19:

and then compile as usual. If you do find an optimal set of Chris@19: CFLAGS for your system, please let us know what they are (along Chris@19: with the output of config.guess) so that we can include them in Chris@19: future releases. Chris@19: Chris@19:

configure supports all the standard flags defined by the GNU Chris@19: Coding Standards; see the INSTALL file in FFTW or Chris@19: the GNU web page. Chris@19: Note especially --help to list all flags and Chris@19: --enable-shared to create shared, rather than static, libraries. Chris@19: configure also accepts a few FFTW-specific flags, particularly: Chris@19: Chris@19:

Chris@19: Chris@19:

To force configure to use a particular C compiler foo Chris@19: (instead of the default, usually gcc), pass CC=foo to the Chris@19: configure script; you may also need to set the flags via the variable Chris@19: CFLAGS as described above. Chris@19: Chris@19: Chris@19: Chris@19: Chris@19: