cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: FFTW 3.3.5: Installation on non-Unix systems cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: cannam@127:
cannam@127:

cannam@127: Next: , Previous: , Up: Installation and Customization   [Contents][Index]

cannam@127:
cannam@127:
cannam@127: cannam@127:

10.2 Installation on non-Unix systems

cannam@127: cannam@127:

It should be relatively straightforward to compile FFTW even on non-Unix cannam@127: systems lacking the niceties of a configure script. Basically, cannam@127: you need to edit the config.h header (copy it from cannam@127: config.h.in) to #define the various options and compiler cannam@127: characteristics, and then compile all the ‘.c’ files in the cannam@127: relevant directories. cannam@127:

cannam@127:

The config.h header contains about 100 options to set, each one cannam@127: initially an #undef, each documented with a comment, and most of cannam@127: them fairly obvious. For most of the options, you should simply cannam@127: #define them to 1 if they are applicable, although a few cannam@127: options require a particular value (e.g. SIZEOF_LONG_LONG should cannam@127: be defined to the size of the long long type, in bytes, or zero cannam@127: if it is not supported). We will likely post some sample cannam@127: config.h files for various operating systems and compilers for cannam@127: you to use (at least as a starting point). Please let us know if you cannam@127: have to hand-create a configuration file (and/or a pre-compiled binary) cannam@127: that you want to share. cannam@127:

cannam@127:

To create the FFTW library, you will then need to compile all of the cannam@127: ‘.c’ files in the kernel, dft, dft/scalar, cannam@127: dft/scalar/codelets, rdft, rdft/scalar, cannam@127: rdft/scalar/r2cf, rdft/scalar/r2cb, cannam@127: rdft/scalar/r2r, reodft, and api directories. cannam@127: If you are compiling with SIMD support (e.g. you defined cannam@127: HAVE_SSE2 in config.h), then you also need to compile cannam@127: the .c files in the simd-support, cannam@127: {dft,rdft}/simd, {dft,rdft}/simd/* directories. cannam@127:

cannam@127:

Once these files are all compiled, link them into a library, or a shared cannam@127: library, or directly into your program. cannam@127:

cannam@127:

To compile the FFTW test program, additionally compile the code in the cannam@127: libbench2/ directory, and link it into a library. Then compile cannam@127: the code in the tests/ directory and link it to the cannam@127: libbench2 and FFTW libraries. To compile the fftw-wisdom cannam@127: (command-line) tool (see Wisdom Utilities), compile cannam@127: tools/fftw-wisdom.c and link it to the libbench2 and FFTW cannam@127: libraries cannam@127:

cannam@127:
cannam@127:
cannam@127:

cannam@127: Next: , Previous: , Up: Installation and Customization   [Contents][Index]

cannam@127:
cannam@127: cannam@127: cannam@127: cannam@127: cannam@127: