1 HOW TO BUILD ARDOUR FROM SOURCE
2 -------------------------------
4 Please: before you do anything else, take a moment to go and join the
5 ardour-dev mailing list (members only). It is very important that the
6 community of people using, testing and developing this software are on
7 the list, and I will NOT deal with questions relating to Ardour's
8 compilation or bugs that are not sent to that list. See
9 http://ardour.org/ for details on joining the mailing list.
11 You can also get in touch with developers and users on IRC. Joining
12 #ardour at irc.freenode.net. The core developers and several key users
13 hang out here on IRC, at pretty much any hour of the night or day.
15 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
17 Full information on building Ardour can be found at:
19 http://ardour.org/building.php
21 Information has been left in this file for those who do not have
22 network access but is not guaranteed to be accurate or up to date.
24 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
30 Please ensure that before attempting to compile Ardour, you have
37 gettext 0.12.1 or above
38 pkgconfig 0.8.0 or above
39 http://www.freedesktop.org/software/pkgconfig/
41 lex and yacc are also required.
42 any version of bison >= 1.35 should work fine.
43 intltool try 0.32 or above
47 Recommended versions, where applicable, are shown under the general
50 JACK 0.99.50 (CVS or snapshot release) (http://jackit.sourceforge.net)
52 libxml2 2.5.X (http://xmlsoft.org/)
56 - available as part of gnome-libs, which you may already
59 - also available via download from GNOME source FTP sites.
60 - see ftp://ftp.gnome.org/pub/GNOME/MIRRORS.html
61 and then follow to sources/libart_lgpl
63 glib 1.2 (http://www.gtk.org)
64 glib-1.2.8 (included with most distributions)
66 GTK+ 1.2 (http://www.gtk.org)
67 gtk+-1.2.8 (included with most distributions)
69 libglade2 (http://www.gnome.org/)
70 unsure of minimum version. XXX todo.
72 libsndfile (http://www.mega-nerd.com/libsndfile/)
73 libsndfile-1.0 or higher
75 libsamplerate (http://www.mega-nerd.com/SRC/)
76 libsamplerate 0.0.13 or higher
78 the LADSPA SDK (http://www.ladspa.org/)
81 raptor (http://librdf.org/raptor/)
83 lrdf (needs raptor) (http://plugin.org.uk/lrdf/)
84 liblrdf 0.4.0 or higher (earlier versions will
85 causes crashes when using plugin presets)
90 The Linux Audio Developers Simple Plugin API (LADSPA) really only
91 consists of a header file, which is already included in the Ardour
94 However, you may want the plugins that come the "full" LADSPA "SDK",
95 so go ahead and download the whole package (it's not big) from
98 I would also recommend getting Steve Harris' excellent set of LADSPA
99 plugins from http://plugin.org.uk/. They make Ardour into a truly
100 useful application. Other LADSPA plugins will be appearing - be sure
101 to watch the Linux Audio Development mailing list for announcements.
103 2A) COMPILING FROM CVS
104 ---------------------
106 Checkout the source from Ardour CVS (the `%' here is meant to be your
109 % cd /usr/local/src # just an example, it can be anywhere
110 % cvs -d:pserver:anoncvs@ardour.org:/cvsroot/ardour login
111 # you will need to contact
112 # paul at linuxaudiosystems dot com
113 # to get the passphrase. See
114 # http://ardour.org/download.html
115 # for details on why this is.
116 % cvs -d:pserver:anoncvs@ardour.org:/cvsroot/ardour -z3 co ardour
118 2B) COMPILING FROM A TARBALL
119 ----------------------------
121 As usual, fetch and unpack the tarball. The directory it creates,
122 ardour-<version>, is referred to below as "$AD".
127 We use the wonderful scons build system, which is started by just typing:
131 in the top level directory of the ardour source tree.
133 To speed things up, on a uniprocessor system, use "scons -j2", and on
134 an SMP system try "scons -j3", which will do a parallel build
135 (constructing more than one thing at a time).
137 If you want to build ardour so that it can be debugged, you may wish
138 to use the DEBUG=yes option. Without it, ardour is built with
139 extreme optimization turned on and the result cannot be debugged
142 If you don't want the installation to happen in the "usual place", add
143 a PREFIX=/my/preferred/prefix option to scons.
145 Compilation takes a while. Running with scons -j3 on a dual PII-450,
146 the entire build takes about 20 minutes, about the same time with
147 scons -j2 on 2.6GHz P4.
149 Other scons options can be discovered using "scons --help"