Chris@10: Next: Cycle Counters, Chris@10: Previous: Installation on Unix, Chris@10: Up: Installation and Customization Chris@10:
It should be relatively straightforward to compile FFTW even on non-Unix
Chris@10: systems lacking the niceties of a configure script. Basically,
Chris@10: you need to edit the config.h header (copy it from
Chris@10: config.h.in) to #define the various options and compiler
Chris@10: characteristics, and then compile all the ‘.c’ files in the
Chris@10: relevant directories.
Chris@10:
Chris@10:
The config.h header contains about 100 options to set, each one
Chris@10: initially an #undef, each documented with a comment, and most of
Chris@10: them fairly obvious. For most of the options, you should simply
Chris@10: #define them to 1 if they are applicable, although a few
Chris@10: options require a particular value (e.g. SIZEOF_LONG_LONG should
Chris@10: be defined to the size of the long long type, in bytes, or zero
Chris@10: if it is not supported). We will likely post some sample
Chris@10: config.h files for various operating systems and compilers for
Chris@10: you to use (at least as a starting point). Please let us know if you
Chris@10: have to hand-create a configuration file (and/or a pre-compiled binary)
Chris@10: that you want to share.
Chris@10:
Chris@10:
To create the FFTW library, you will then need to compile all of the
Chris@10: ‘.c’ files in the kernel, dft, dft/scalar,
Chris@10: dft/scalar/codelets, rdft, rdft/scalar,
Chris@10: rdft/scalar/r2cf, rdft/scalar/r2cb,
Chris@10: rdft/scalar/r2r, reodft, and api directories.
Chris@10: If you are compiling with SIMD support (e.g. you defined
Chris@10: HAVE_SSE2 in config.h), then you also need to compile
Chris@10: the .c files in the simd-support,
Chris@10: {dft,rdft}/simd, {dft,rdft}/simd/* directories.
Chris@10:
Chris@10:
Once these files are all compiled, link them into a library, or a shared Chris@10: library, or directly into your program. Chris@10: Chris@10:
To compile the FFTW test program, additionally compile the code in the
Chris@10: libbench2/ directory, and link it into a library. Then compile
Chris@10: the code in the tests/ directory and link it to the
Chris@10: libbench2 and FFTW libraries. To compile the fftw-wisdom
Chris@10: (command-line) tool (see Wisdom Utilities), compile
Chris@10: tools/fftw-wisdom.c and link it to the libbench2 and FFTW
Chris@10: libraries
Chris@10:
Chris@10:
Chris@10:
Chris@10: