BUILDING FROM SOURCE
~~~~~~~~~~~~~~~~~~~~
Do ./configure, optionally with --with-perl, --with-python and --with-lame, 
if you want support for them (but configure will try to detect them
automatically).

If for some reason the configure script doesn't find the include files for
python, perl or lame, you have to specify the path to these with
--with-something-includes and --with-something-libraries.

./configure --help will help you out with the exact syntax for those options.

To configure it all on my debian/sid system with python 2.1, I use
./configure --with-python-includes=/usr/include/python2.1

I installed lame as a debian package so lame.h is in /usr/include/lame/lame.h
and libmp3lame.a is in /usr/lib. configure finds everything automatically.

Then, do 'make' and everything should be fine.

Optionally do a 'make install' which installs all the ices stuff.

BUILDING FROM CVS
~~~~~~~~~~~~~~~~~
If you're installing ices from cvs, you need to do something
like this:

cvs co ices
cd ices
cvs co libshout

./autogen.sh
make

And you'll hopefully have a ices binary in src/

For configfiles, ices depends on libxml, and I've
only tested it with libxml version 2.
Make sure you've got xml-config in your path and
that setup should be fine.

For playlist handlers, ices can optionally use
python or perl.
Add --with-python or --with-perl, to the configure script if you
want this enabled.

For reencoding, you'll need libmp3lame, and the --with-lame* options
in configure. That works fine for me most of the time, but I wouldn't
exactly call it stable.

Check the ./configure --help options for this.

Good luck.
