annotate wiki/Building.wiki @ 316:66a23c0545b6

-Added MFCCs back to the feature generation script
author tomwalters
date Thu, 04 Mar 2010 17:38:58 +0000
parents 0ae1d8df7bbd
children db6d540cf541
rev   line source
tomwalters@270 1 #summary Building AIM-C
tomwalters@270 2 #labels Phase-Design
tomwalters@270 3
tomwalters@270 4 = Introduction =
tomwalters@270 5
tomwalters@270 6 AIM-C is built using the [http://www.scons.org/ SCons] build system. SCons is multiplatform, and is based on Python.
tomwalters@270 7
tomwalters@270 8 = Build Environment =
tomwalters@270 9 One of the major requirements of AIM-C is that it is written, as far as possible, in standard C++ (including some heavy dependence on the standard library). This means that (in theory at least) it will compile under any reasonably sane C++ compiler. In practice, so far development has taken place mainly using GCC on Mac OS 10.6.
tomwalters@270 10
tomwalters@270 11 = External Dependencies =
tomwalters@270 12 None as yet.
tomwalters@270 13
tomwalters@270 14 The project uses [http://code.jellycan.com/simpleini/ simpleini] version 4.12 for storing, parsing and writing out parameters files, but this file (and the UTF support code that it requires) is included in the source repository.
tomwalters@270 15
tomwalters@270 16 The original command-line version of AIM-C had dependencies on
tomwalters@270 17 * [http://www.mega-nerd.com/libsndfile/ libsndfile] for audio file input.
tomwalters@270 18 * [http://www.portaudio.com/ PortAudio] for live audio input.
tomwalters@270 19 * [http://www.fftw.org/ FFTW3] for FFTs
tomwalters@270 20
tomwalters@270 21 The libsndfile and portaudio input classes will eventually be ported over to the current version. The dependence on FFTW will likely be dropped, as the FIR gammatone filterbank from the original version is the only filterbank that uses FFT routines, and a basic FFT will likely be fast enough in place of FFTW.
tomwalters@270 22
tomwalters@270 23 = Build Tools =
tomwalters@270 24 == Building ==
tomwalters@270 25
tomwalters@270 26 Assuming SCons is installed, to build the source tree simply navigate to the top level of the source tree (where the SConstruct file resides) and issue the command:
tomwalters@270 27
tomwalters@270 28 `scons`
tomwalters@270 29
tomwalters@270 30 == Getting SCons ==
tomwalters@270 31 On GNU/Linux systems, either use your favourite package manager to install scons, for example on Debian / Ubuntu:
tomwalters@270 32
tomwalters@270 33 `sudo apt-get install scons`
tomwalters@270 34
tomwalters@270 35 On Mac OS X, I'd recommend using MacPorts. It's a handy way of installing all sorts of free software. First install MacPorts, then run the command:
tomwalters@270 36
tomwalters@270 37 `sudo port install scons`
tomwalters@270 38
tomwalters@270 39 Alternatively, in either case, you can just download and install a tarball from the [http://www.scons.org/ SCons site].
tomwalters@270 40
tomwalters@270 41 (TODO) On Windows...