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
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
|
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.
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.
Mac OS X pre-requisites
=======================
Detailed build instructions are available at
http://mumble.sourceforge.net/BuildingMacOSX and it is highly recommended
to follow them to the letter.
Linux pre-requisites
====================
Detailed build instructions are available at
http://mumble.sourceforge.net/BuildingLinux and it is highly recommended
to follow them to the letter.
Please note that in addition to the depending libraries, you also need
lsb_release installed.
Building Mumble and Murmur
==========================
To build mumble and murmur, type
qmake main.pro
make release
You may need to edit src/mumble/mumble.pro to reflect the installation paths you
use for libraries.
After building, the binaries will be in the release/ directory.
The qmake step supports a number of configurations options. To enable an
option, simply add CONFIG+=<option> to the end. If you want to change these
after your initial setup, you'll also need to pass -recursive.
So, to build without the server and without ASIO, the above line would be
qmake main.pro CONFIG+=no-server CONFIG+=no-asio -recursive
CONFIG+=no-client
Don't build the client (Mumble)
CONFIG+=no-server
Don't build the server (Murmur)
CONFIG+=no-bundled-speex
Don't use the included version of Speex, but look for one on the system.
Note that this requires your system-installed Speex to be at least version
1.2.0.
CONFIG+=optimize
Build a heavily optimized version, specific to the machine it's being
compiled on.
CONFIG+=universal (OSX)
Builds an universal-binary build of Mumble for i386 and ppc instead of the
default x86-64-only build. The universal build is meant to be used with
the Carbon version of Qt, and is compatible with 10.4+.
The x86-64 build of Mumble is compatible with 10.5+ and requires a Cocoa
version of Qt.
CONFIG+=no-dbus (Mumble)
Don't include DBus support on Mumble. This has no effect on Murmur, which
requires DBus to work.
CONFIG+=no-g15 (Mumble)
Don't include support for the G15 keyboard (and compatible devices).
CONFIG+=no-asio (Mumble, Win32)
Don't build support for ASIO audio input.
CONFIG+=no-directsound (Mumble, Win32)
Don't build support for DirectSound.
CONFIG+=no-wasapi (Mumble, Win32)
Don't build support for WASAPI.
CONFIG+=no-portaudio (Mumble, Unix, OSX)
Don't build support for PortAudio.
CONFIG+=no-pulseaudio (Mumble, Unix)
Don't build support for PulseAudio.
CONFIG+=no-oss (Mumble, Linux)
Don't build support for OSS. Mumble supports OSS4 if you have the correct
header files.
CONFIG+=no-alsa (Mumble, Linux)
Don't build support for ALSA.
CONFIG+=no-speechd (Mumble, Linux)
Don't build support for Speech Dispatcher.
CONFIG+=no-update (Mumble)
Default disable the checking of new versions. (For distributions)
CONFIG+=no-embed-qt-translations (Mumble)
Don't embed the translations for Qt, load them from the system. (For
distributions).
CONFIG+=no-ice (Murmur)
Don't build support for Ice RPC.
CONFIG+=no-bonjour
Don't build support for Bonjour.
CONFIG+=no-overlay (Mumble, Linux)
Don't build the overlay library.
User Registrations
==================
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.
|
