Introduction

Mumble has quite a few dependencies for building on Windows, and as the feature set grows, so does the list of dependencies. This page will try to detail the steps required to set up a Win32 build environment suitable for compiling the current code found in our repository. Be aware that this steps might not work for older revisions of Mumble as dependencies might have been removed or updated to an incompatible version in the meantime.

The paths used here equal the defaults assumed in the Mumble build files. You are free to change them, but you might need to adjust the build files themselves. If you find any problems or incorrect steps in this article please either correct them or contact us and we will try our best to resolve the issue.

Also note, that if you are submitting a bug report for a self-built executable, we expect you to either

Follow these instructions to the letter

or

Report any deviations from these instructions

Deviations means anything, from "I installed to the D: drive" to "I changed the gcc build options for Qt" or "I used another version of Speex".

Intel C++ Compiler

This is strictly optional and you can compile a perfectly working version of Mumble without this compiler following this guide. This guide does not give information on how to use the Intel compiler with VS2008 to compile Mumble, so you will need to either have the programming experience necessary to know how to do this or find the procedures to do so elsewhere.

Start a new command shell (run cmd.exe) (Make sure you have Microsoft Visual C++ and Git installed before you run prep!)

cd \dev
prep

After you run prep make sure a message similar to "Setting environment for using Microsoft Visual Studio 2008 x86 tools" appears.

Whenever something appears

like this

you're supposed to enter it in that command shell (or copy it from this webpage and right click in the command window and select Paste). When you later want to compile things, remember to call prep.bat first to set paths correctly.

Note to those following this guide: When you extract compressed files, sometimes they will have container folders and sometimes they will not. Please ensure (for example) that when you extract a compressed file like QT4.5.1, that you see "bin" "include" and such folders as that directly inside of the folder named "Qt4.5.1". If you just see one folder and no other files, you have done it wrong.

This might take a while, but when done you'll have Boost installed.
Note that none of the other build dependencies do themselves depend on boost, so if you want you can just continue in a new command shell (but remember to call prep.bat). Once all is done, you can safely delete the boost_1_41_0 and boost-jam directories. If you get the warning, that some targets were skipped or failed, it can be ignored for our purposes.

As you are going through the installer you will come to a window where you will see two main categories and then subcategories below them. Uncheck the green check boxes next to “Documentation” and “Samples”. Continue with the installation. These take a long time to download and are not really needed for Mumble.

WinDBUS

Whereas * represents the newest version on the server. Unpack all of them to 'c:\Program Files\win32libs'. If you have extracted them all correctly you should see inside of 'c:\Program Files\win32libs' "include," bin," lib," and "manifest" folders. Note that you may also download the dbus library from there, but if you do it will not automatically spawn dbus-daemon as that needs patching.

Download CMake and unpack it to c:\dev. Rename the top directory to just 'cmake'.

Protocol Buffers

Download Protocol Buffers from Google (protobuf-x.y.z.zip) and unpack it to c:\dev\protobuf-z.y.z. Follow the documentation in c:\dev\protobuf-x.y.z\vsprojects\readme.txt. Note that if the release number changes you will need to change prep.bat to whatever z.y.z changed to or you won't be able to call protoc.exe.

libogg

If you want to compile Mumble 1.1.x, you need to go to C:\dev\libogg\win32\VS2008, build the release builds of libogg, and copy C:\dev\libogg\win32\VS2008\Win32\Release_SSE2\libogg.lib to the new Folder C:\dev\libogg\lib\.

Note: This dependency is not needed if you do not want to compile the Mumble compatibility client (Mumble 1.1.x). The Mumble compatibility client can be disabled by passing CONFIG+=no-11x to qmake. This dependency is not needed for building the server.

ZeroC Ice

Note: Ice can be disabled by passing CONFIG+=no-ice to qmake. Bear in mind that the Ice RPC Interface is the recommended way to control the server. This dependency is not needed for building the client.

Download Mumble and Submodules

To use the v1.1.x branch (which you most likely do) run this command after running the commands above:

git checkout --track -b v1.1.x origin/v1.1.x

If you are using the current branch, you will need to open git bash and cd to the mumble folder that was created. Now cd to

src/mumble11x

and then do

sh mklinks.sh

Building Mumble and Murmur

Once all of the above is done we can get to compiling Mumble itself.

If you want to have ASIO support you have to install an additional, proprietary, ASIO SDK.

There are four dependencies that most people who make their own compiles will not need: g15, asio, bonjour, and 11x. The bonjour dependency is useful if you want to browse servers across a local network, but you can disable it if this feature is not needed.

To compile Mumble without Mumble 1.1.x, ASIO, G15, and Bonjour, replace the qmake command below with this one:

To compile Mumble with Mumble 1.1.x, but without ASIO, Bonjour, and G15 replace the qmake command below with this one:

qmake CONFIG+=no-asio CONFIG+=no-bonjour CONFIG+=no-g15 -recursive

Note that the compile will fail if you leave out these build flags and do not have the SDK required.

To compile Mumble:

cd \dev
prep
cd mumble
qmake
nmake clean
nmake

Note that this builds the debug versions, which is what we strongly recommend to use while developing. If you want to send the binary to someone else, use

nmake release

instead of the last

nmake

command listed above. This will result in a much smaller binary with fewer dependencies.

Running Mumble and Murmur

Once compiled, you can go into c:\dev\mumble\release or (\debug if you compiled the debug version) and can execute mumble.exe or murmur.exe. Before executing Mumble or Murmur you need to open a command prompt and do

cd \dev
prep
cd mumble\debug (or release)

Then execute either Mumble or Murmur from the command prompt with

mumble.exe

or

murmur.exe

If you want to run the release build directly from Windows Explorer, you will need to collect all the library files into one folder, along with the executables you built when you compiled Mumble. Have a look at the files the official Mumble installer creates in Program Files\Mumble to find out which files you will need.