Installing From Source

This page briefly describes building and installing AniComp. Currently, AniComp is Linux only at this stage.


First of all, check that the you have met the requirements. Most are fairly standard libraries that should be available for your system through your package manager.

Cutil is an exception, and is available only via the subversion repository at this time. A quick installation guide is availble for cutil.

The listed requirements relate to the development version of AniComp, if you are using the AniComp-0.0.1 snapshot, you will also require libboost, specifically the filesystem library.


AniComp uses the standard autotools to build. As you will be building the application from source, you are going to need a compiler.

If you are building from CVS, you are also going to require a few extra tools.

Get the Source

Get the latest file release from the download page .

Alternatively, grab the latest development directly from CVS (coming soon). When promted for a password, simply hit return. This will retieve the current CVS snapshot from the Sourceforge CVS server and place it into the newly create directories animix/anicomp.

# cvs login
# cvs -z3 co -P animix/anicomp

You can periodically update your local copy of the CVS tree using;

# cvs update

Building from CVS

If you intend to build from CVS, you will to bootstrap the source tree. A small shell script, bootstrap, is contained within the source tree to handle a few initial steps (running aclocal, automake, autoconf etc.). Run the script now.

# ./bootstrap

The bootstrap script may give some warning messages regarding under quoted definitions. These messages can be safely ignored, they are not connected with AniComp.

The Configure Script

If you are using a snapshot release of AniComp, untar the archive now.

# tar -zxvf AniComp-<release>.tar.gz

Now that we have a bootstraped source tree, we are ready to configure the sources. To review any specific configure time options, run

# ./configure --help

At this stage, we are not interested in any options other than the installtion prefix. This controls where AniComp will be installed. The default is /usr/local/ and will require root access to install. We can specify an aternative prefix using

# ./configure --prefix=/path/to/install

(Finer control over install directories is not covered here, see configure --help for details.)

Depending on where you have instlled cutil, you may need to update your PKG_CONFIG_PATH environment variable. If you choose to install cutil outwith the default location, /usr/local. you will need to point the variable at the pkgconfig directory of the cutil install. You can update the environment temporarily with the following command.

# export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/path/to/cutil/instal/lib/pkgconfig

(Notice there is no trailing / character)

We are now ready to configure the sources with an optional prefix.

# ./configure --prefix=/path/to/install

The configure script should complete without any trouble, if not, get in touch


Assuming the configure script suceeded, we are now ready to build AniComp.

# make

Assuming there were no build errors (if there are, get in touch) , we can install the application.

# make install

Note: to install into certain locations you will need root access. If this is not available, specifiy a build prefix to configure that is writable.


Congratulations, you've just built AniComp.

The Quick Intro gives a brief description of setting up, and starting a new animatic session.