Mercurial > hg > js-dsp-test

annotate fft/fftw/fftw-3.3.4/doc/html/Installation-on-non_002dUnix-systems.html @ 40:223f770b5341 kissfft-double tip

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Try a double-precision kissfft
author Chris Cannam
date Wed, 07 Sep 2016 10:40:32 +0100
parents 26056e866c29
children
rev   line source
Chris@19 1 <html lang="en">
Chris@19 2 <head>
Chris@19 3 <title>Installation on non-Unix systems - FFTW 3.3.4</title>
Chris@19 4 <meta http-equiv="Content-Type" content="text/html">
Chris@19 5 <meta name="description" content="FFTW 3.3.4">
Chris@19 6 <meta name="generator" content="makeinfo 4.13">
Chris@19 7 <link title="Top" rel="start" href="index.html#Top">
Chris@19 8 <link rel="up" href="Installation-and-Customization.html#Installation-and-Customization" title="Installation and Customization">
Chris@19 9 <link rel="prev" href="Installation-on-Unix.html#Installation-on-Unix" title="Installation on Unix">
Chris@19 10 <link rel="next" href="Cycle-Counters.html#Cycle-Counters" title="Cycle Counters">
Chris@19 11 <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
Chris@19 12 <!--
Chris@19 13 This manual is for FFTW
Chris@19 14 (version 3.3.4, 20 September 2013).
Chris@19 15
Chris@19 16 Copyright (C) 2003 Matteo Frigo.
Chris@19 17
Chris@19 18 Copyright (C) 2003 Massachusetts Institute of Technology.
Chris@19 19
Chris@19 20 Permission is granted to make and distribute verbatim copies of
Chris@19 21 this manual provided the copyright notice and this permission
Chris@19 22 notice are preserved on all copies.
Chris@19 23
Chris@19 24 Permission is granted to copy and distribute modified versions of
Chris@19 25 this manual under the conditions for verbatim copying, provided
Chris@19 26 that the entire resulting derived work is distributed under the
Chris@19 27 terms of a permission notice identical to this one.
Chris@19 28
Chris@19 29 Permission is granted to copy and distribute translations of this
Chris@19 30 manual into another language, under the above conditions for
Chris@19 31 modified versions, except that this permission notice may be
Chris@19 32 stated in a translation approved by the Free Software Foundation.
Chris@19 33 -->
Chris@19 34 <meta http-equiv="Content-Style-Type" content="text/css">
Chris@19 35 <style type="text/css"><!--
Chris@19 36 pre.display { font-family:inherit }
Chris@19 37 pre.format { font-family:inherit }
Chris@19 38 pre.smalldisplay { font-family:inherit; font-size:smaller }
Chris@19 39 pre.smallformat { font-family:inherit; font-size:smaller }
Chris@19 40 pre.smallexample { font-size:smaller }
Chris@19 41 pre.smalllisp { font-size:smaller }
Chris@19 42 span.sc { font-variant:small-caps }
Chris@19 43 span.roman { font-family:serif; font-weight:normal; }
Chris@19 44 span.sansserif { font-family:sans-serif; font-weight:normal; }
Chris@19 45 --></style>
Chris@19 46 </head>
Chris@19 47 <body>
Chris@19 48 <div class="node">
Chris@19 49 <a name="Installation-on-non-Unix-systems"></a>
Chris@19 50 <a name="Installation-on-non_002dUnix-systems"></a>
Chris@19 51 <p>
Chris@19 52 Next:&nbsp;<a rel="next" accesskey="n" href="Cycle-Counters.html#Cycle-Counters">Cycle Counters</a>,
Chris@19 53 Previous:&nbsp;<a rel="previous" accesskey="p" href="Installation-on-Unix.html#Installation-on-Unix">Installation on Unix</a>,
Chris@19 54 Up:&nbsp;<a rel="up" accesskey="u" href="Installation-and-Customization.html#Installation-and-Customization">Installation and Customization</a>
Chris@19 55 <hr>
Chris@19 56 </div>
Chris@19 57
Chris@19 58 <h3 class="section">10.2 Installation on non-Unix systems</h3>
Chris@19 59
Chris@19 60 <p>It should be relatively straightforward to compile FFTW even on non-Unix
Chris@19 61 systems lacking the niceties of a <code>configure</code> script. Basically,
Chris@19 62 you need to edit the <code>config.h</code> header (copy it from
Chris@19 63 <code>config.h.in</code>) to <code>#define</code> the various options and compiler
Chris@19 64 characteristics, and then compile all the &lsquo;<samp><span class="samp">.c</span></samp>&rsquo; files in the
Chris@19 65 relevant directories.
Chris@19 66
Chris@19 67 <p>The <code>config.h</code> header contains about 100 options to set, each one
Chris@19 68 initially an <code>#undef</code>, each documented with a comment, and most of
Chris@19 69 them fairly obvious. For most of the options, you should simply
Chris@19 70 <code>#define</code> them to <code>1</code> if they are applicable, although a few
Chris@19 71 options require a particular value (e.g. <code>SIZEOF_LONG_LONG</code> should
Chris@19 72 be defined to the size of the <code>long long</code> type, in bytes, or zero
Chris@19 73 if it is not supported). We will likely post some sample
Chris@19 74 <code>config.h</code> files for various operating systems and compilers for
Chris@19 75 you to use (at least as a starting point). Please let us know if you
Chris@19 76 have to hand-create a configuration file (and/or a pre-compiled binary)
Chris@19 77 that you want to share.
Chris@19 78
Chris@19 79 <p>To create the FFTW library, you will then need to compile all of the
Chris@19 80 &lsquo;<samp><span class="samp">.c</span></samp>&rsquo; files in the <code>kernel</code>, <code>dft</code>, <code>dft/scalar</code>,
Chris@19 81 <code>dft/scalar/codelets</code>, <code>rdft</code>, <code>rdft/scalar</code>,
Chris@19 82 <code>rdft/scalar/r2cf</code>, <code>rdft/scalar/r2cb</code>,
Chris@19 83 <code>rdft/scalar/r2r</code>, <code>reodft</code>, and <code>api</code> directories.
Chris@19 84 If you are compiling with SIMD support (e.g. you defined
Chris@19 85 <code>HAVE_SSE2</code> in <code>config.h</code>), then you also need to compile
Chris@19 86 the <code>.c</code> files in the <code>simd-support</code>,
Chris@19 87 <code>{dft,rdft}/simd</code>, <code>{dft,rdft}/simd/*</code> directories.
Chris@19 88
Chris@19 89 <p>Once these files are all compiled, link them into a library, or a shared
Chris@19 90 library, or directly into your program.
Chris@19 91
Chris@19 92 <p>To compile the FFTW test program, additionally compile the code in the
Chris@19 93 <code>libbench2/</code> directory, and link it into a library. Then compile
Chris@19 94 the code in the <code>tests/</code> directory and link it to the
Chris@19 95 <code>libbench2</code> and FFTW libraries. To compile the <code>fftw-wisdom</code>
Chris@19 96 (command-line) tool (see <a href="Wisdom-Utilities.html#Wisdom-Utilities">Wisdom Utilities</a>), compile
Chris@19 97 <code>tools/fftw-wisdom.c</code> and link it to the <code>libbench2</code> and FFTW
Chris@19 98 libraries
Chris@19 99
Chris@19 100 <!-- -->
Chris@19 101 </body></html>
Chris@19 102