3. Installation

This chapter describes how to get LADCCA installed on your system.

3.1 Dependencies

LADCCA depends on the ALSA library, the JACK library, a unique ID library called libuuid and the XML library libxml2. You need these installed before attempting to install LADCCA.

ALSA is available from http://www.alsa-project.org/.

JACK is available from http://jackit.sf.net/.

The libuuid library is included with the ubiquitous e2fsprogs package, but if this is not installed on your system, it is available from http://e2fsprogs.sf.net/. The libxml2 library is available from http://www.xmlsoft.org/.

The LADCCA Control client depends on the GNU Readline library, available from ftp://ftp.gnu.org/pub/gnu/readline/.

The LADCCA GTK Test Client and the LADCCA Save Button 2 client both depend on the GTK+ 2 toolkit, available from ftp://ftp.gtk.org/pub/gtk/v2.0/. The LADCCA Synth client has an optional GUI which also uses the GTK+ 2 toolkit.

The LADCCA Save Button client depends on the GTK+ 1.2 toolkit, also available from ftp://ftp.gtk.org/pub/gtk/v1.2/.

3.2 Installation

First off, you need to download the package. It is available from the LADCCA webpage, http://pkl.net/~node/ladcca.html. After you have downloaded it, unpack the tarball into a directory using @command{tar xzf /where/ever/you/put/ladcca-0.4.0.tar.gz} and change into the source directory with @command{cd ladcca-0.4.0}.

The package uses the GNU autotools for configuration and makefile creation. In order to install the package, you must complete three steps: configuration; building; and installing.

3.2.1 Configuration

To configure the package, there is a shell script named `configure' in the top source directory. It is a standard GNU autoconf configure script, and so accepts the standard GNU configuration options (such as @option{--prefix}, @option{--datadir}, etc.) To run it type @command{./configure} and add any options. The non-standard options that the script recognises are described below. Running the script with the @option{--help} option will also provide a quick summary of the recognised options.

3.2.1.1 Configure script options

@option{--disable-gtk2}

Prevents the configure script from checking for the presence of the GTK+ 2 toolkit and disables the building of any code that relies on it. The LADCCA Save Button 2 and LADCCA GTK Test Client both rely on GTK+ 2.

@option{--disable-gtk}

Prevents the configure script from checking for the presence of the GTK+ 1.2 toolkit and disables the building of any code that relies on it. The LADCCA Save Button client relies on GTK+ 1.2.

@option{--enable-debug}

Causes the library, server and clients to be built with debugging output. This is not very useful and only recommended for developers working on the LADCCA code itself.

@option{--with-default-dir=DIR}

Specifies the default directory, relative to \$HOME under which the server will create new project directories. Without this option, the value defaults to `audio-projects'.

@option{--disable-serv-inst}

The LADCCA server and library look up port addresses for the LADCCA service using standard system calls that refer to the `/etc/services' database. If `/etc/services' does not contain a valid entry, an error will result. By default, the installation routine will install a service entry if one does not exist. This flag disables that action.

3.2.2 Building

To build the package, simply type @command{make} in the top source directory. This will build the server, the library and the clients that are compatible with the resources found by the configure script.

3.2.3 Installing

To install the package, type @command{make install} in the top source directory. By default the package installation prefix is `/usr/local' but the @option{--prefix} option to the configure script will change this. The @command{ladccad} server and the clients that were built are installed in `prefix/bin'. The libladcca client library is installed in `prefix/lib'. The C header files for the client library are installed under `prefix/include'. This manual is installed under `prefix/info'.

With @command{make install}, the package is installed with debugging symbols in the object files. To save space, you can install with @command{make install-strip} to install the object files without debugging symbols.

Go to the first, previous, next, last section, table of contents.