## 9. Appendix I: Building Matchbox from source.

Firstly its recommended if your not used to building software from source, you should check your distribution for pre built binary matchbox packages.

All Matchbox packages use GNU autotools and are configured and build by the usual;

    	% ./configure
    	% make
    	% sudo make install

You can see the various compile time options for enabling extra features and dependencies by running.

    	% ./configure --help

### 9.1. Inter Dependencies

Virtually all packages are dependant on libmatchbox. You should build and install libmatchbox first. All font and image operations are provided to other matchbx packages via libmatchbox. Therefore the configure options you choose here ( such as Pango, JPEG support ) will affect dependant packages.

Matchbox-window-manager can be built without libmatchbox using the --enable-standalone options. It is highly recommeded you only do this is you intend to run only the window manager with no bells and whistles such as themeing. This build option is intended mainly for platforms where resources are very low or you want a quick and dependency free window manager for testing on a new platform.

If you decide to install the matchbox-panel or matchbox-desktop packages you should install the matchbox-common package first. It contains icons and launcher configuration data shared by both the desktop and the panel menu launcher.

If you encounter problems building, please report to the mailing list for help.

### 9.2. Automated building

An automated build script is available to ease the build process. This will build a fully featured matchbox environment including the window manager, desktop, panel and panel applications.

Download matchbox-autobuild.sh script. Open in your favorite text editor, edit the variables at the top of the top and then run.

### 9.3. Building from SVN

If you plan on building from SVN, then before you build;

- autoconf --version must report 2.5 or later

- automake --version must report 1.7.x

- libtool --version must report 1.5 (available from http://ftp.club.cc.cmu.edu/\pub/gnu/libtool/libtool-1.5.tar.gz if your distribution doesn't have it)

- pkg-config --version must report 0.9.0 or later

You will also need GConf2 Development packages and Check installed ( These are only needed if building from SVN, optional if building from release tarballs ).