Next: , Previous: Installing from a Source Tarball, Up: Installing

2.3 Installing from the SVN Repository

The SVN install is a bit more complicated to compile and install than the source tarball.

2.3.1 SVN Install Requirements

This SVN source code is much more complicated than the source install described above. You should only try to build this if you want to build everything completely from scratch. Be prepared to run into a few glitches, especially when building the documentation.

The development build requires that several more dependencies be installed first. You must download the source using Subversion as described above. Your computer must also have a C++ compiler such as GCC or Apple's Xcode and recent versions of the following:

To install these, follow the instructions for each individual package or use a package manager such as Fink, MacPorts or Cygwin. The following commands must be in your path and executable from the command line: lilypond, swig, convert, dot, sbcl, cm and xmllint as well as all of the autoconf and texinfo tools and the C compiler. Many of these dependencies are required by the documentation build and regression test. If you don't plan on building these, then only swig, the autoconf tools and C compiler needs to be in your path.

2.3.2 Repository Checkout

To checkout the sources from the SVN repository type the following at a command prompt:

     cd path/to/installfrom/directory
     svn co fomus

This creates a fomus directory and downloads the latest development source tree into it.

You can also checkout releases snapshots, which are much more stable and reliable than the trunk. The following command lists all of the releases currently stored in the repository:

     svn ls

After you've selected the version you want, the command to check it out is then:

     cd path/to/installfrom/directory
     svn co fomus

2.3.3 Compiling and Installing from the SVN Repository

Before compiling, you must run Autoconf and related tools first. There is a shell script called bootstrap that does this for you and reports whether or not it succeeded.

     cd path/to/fomus/source/directory

If the Autoconf Archive doesn't come with your system or distribution then download/unpack it somewhere and add the path to the m4 directory (located inside the archive) to the ./bootstrap command. If you've unpacked the archive in /usr/local/src, for example, you should then type something like this in place of what is shown above:

     ./bootstrap /usr/local/src/autoconf-archive-2008-11-07/m4

If that doesn't work, use the following commands at a command prompt:

     cd path/to/fomus/source/directory
     automake -a

If you've untarred the Autoconf Archive somewhere then type something similar to the following instead:

     cd path/to/fomus/source/directory
     aclocal -I /usr/local/src/autoconf-archive-2008-11-07/m4
     automake -a
     ACLOCAL="aclocal -I /usr/local/src/autoconf-archive-2008-11-07/m4" autoreconf

It is okay if aclocal, libtoolize and automake complain about missing files, etc.. The final autoreconf command should run cleanly without any output. On Mac OS X, libtool is prefixed with the letter g (e.g., type glibtoolize instead of libtoolize). After this you will only need to type autoreconf to repeat this step (including the ACLOCAL environment variable if necessary). However, this probably won't be necessary since make should take care of any necessary autoreconfing.

At this point, follow the instructions for the compiling and installing from the source tarball above.

2.3.4 Updating SVN Installation

To update the source tree, type:

     cd path/to/fomus/source/directory
     make uninstall
     svn up

It is important to uninstall FOMUS first to insure that any old modules are deleted and won't get in the way of the new install. After updating the source files type make and make install to compile and reinstall the updated sources.