[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3 Installation

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


[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3.1 Dependencies

LASH 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 LASH.

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 LASH Control client depends on the GNU Readline library, available from ftp://ftp.gnu.org/pub/gnu/readline/.

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


[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3.2 Installation

First off, you need to download the package. It is available from the LASH webpage, http://www.nongnu.org/lash. After you have downloaded it, unpack the tarball into a directory using tar -xzf /where/ever/you/put/lash-0.5.4.tar.gz and change into the source directory with cd lash-0.5.4.

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.


[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

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 ‘--prefix’, ‘--datadir’, etc.) To run it type ./configure and add any options. The non-standard options that the script recognises are described below. Running the script with the ‘--help’ option will also provide a quick summary of the recognised options.


[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3.2.1.1 Configure script options

--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.

--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 LASH code itself.

--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’.


[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3.2.2 Building

To build the package, simply type 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.


[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3.2.3 Installing

To install the package, type make install in the top source directory. By default the package installation prefix is ‘/usr/local’ but the ‘--prefix’ option to the configure script will change this. The lashd server and the clients that were built are installed in ‘prefix/bin’. The liblash 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 make install, the package is installed with debugging symbols in the object files. To save space, you can install with make install-strip to install the object files without debugging symbols.


[ << ] [ >> ]           [Top] [Contents] [Index] [ ? ]

This document was generated on January 30, 2020 using texi2html 5.0.