INSTALL


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66


Binary versions
===============

Binary versions for Win32 of the most recent version of mumble are provided
on sourceforge.net, see http://www.sourceforge.net/projects/mumble/

The only legitimate releases of Mumble will be on sourceforge, any other
place offering Mumble is likely to contain trojans or viruses.

Pre-requisites
==============

Mumble and murmur depends on Qt version 4.3.0 or above; either the opensource
or commercial versions will do.
Please see http://www.trolltech.com/qt/ for more information. As we use the Qt
build system, it's important that you have a fully functional Qt installation.

The mumble build uses pre-comiled headers. If you use GCC, make sure it's at
least version 3.4, and preferably 4.2 or newer.

Mumble needs the Boost C++ library. http://www.boost.org

You may need to adjust the paths in mumble.pro, murmur.pro and mumble.pri to
reflect where your installed versions of dependant libraries are.

Windows pre-requisites
======================

Detailed build instructions are available at
http://mumble.sourceforge.net/BuildingWindows and it is highly recommended
to follow them to the letter.

Linux pre-requisites
====================

Mumble needs libasound2 (the ALSA developer libraries) as well as the developer
libraries for Xevie.

The Linux version of the client is developed on Ubuntu 7.10. It may work on
other updated distributions. The server should work on any modern UNIX-based
distribution and on Windows.

Building Mumble and Murmur
==========================

To build mumble and murmur, type
qmake main.pro
make

You may need to edit src/mumble/mumble.pro to reflect the installation paths you
use for libraries.

Building only Murmur
====================

To build only murmur, type
qmake main.pro CONFIG+=no-client
make

To enable user registration, copy scripts/murmur.pl to murmur.cgi and put it
somewhere accessible by your webserver. Make sure your webserver is 
configured to execute it as a CGI, and make sure you edit it to reflect
the configuration parameters. Note that the user the CGI will run as needs
write permissions to both the database file and the directory the database
file resides in.