From Mumble Wiki
Revision as of 13:41, 29 February 2008 by Slicer (talk | contribs)
Jump to: navigation, search

Transitions to MSVC

I'm attempting to transition Mumble to build with MSVC, including the free Express edition. This will allow us to use new platform features (such as advanced audio on Vista) which are unavailable under mingw.

As such, this documentation is completely out of sync with reality, and until this notice is gone, they most likely will not work. You've been warned.

Building Mumble on Windows

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.

The paths used here equal the defaults assumed in the Mumble build files. You are free to change them, but you'll then need to change the file as well.

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

  • Follow these instructions to the letter


  • 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".


Create C:\dev, and inside that directory create a file prep.bat containing:

@echo off
SET QTDIR=C:\dev\Qt4.3.4
SET DBUSDIR=C:\dev\dbus
SET PATH=C:\dev\MinGW\bin;%QTDIR%\bin;%DBUSDIR%\bin;C:\dev\openssl\out;C:\dev\openssl;C:\dev\cmake\bin;%PATH%

Start a new command shell (run cmd.exe) and

CD \dev

Whenever something appears

like this

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

Using your computer while compiling

Compilation is a almost 100% CPU bound job. The windows task switcher doesn't really understand that this isn't really an interactive application, and hence will happily make your entire desktop quite laggy just to gain 1% on the compile time. It is therefore recommended to open your task manager (Ctrl-Alt-Del), switch to Processes, locate cmd.exe, rightclick, Set Priority, BelowNormal. And answer Yes. Doing so will make sure your interactive things get priority. Note, however, that if you do other 100% cpu bound things (like play resource-intensive games), compilation will halt until you're done.


Download the most recent version of TortoiseSVN at and install it. The defaults are fine.

Download Mumble SVN

Open c:\dev, rightclick and SVN Checkout...

Repository is

checkout to C:\dev\mumble\


Download and and unzip both to C:\dev\

cd \dev\boost_1_34_1
copy ..\boost-jam-3.1.14-1-ntx86\bjam.exe
bjam --toolset=gcc --prefix=C:\dev\Boost install

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_34_1 and boost-jam directories. If you get the warning, that some targets were skipped or failed, it can be ignored for our purposes.

Microsoft Windows SDK

Go to and search for the Windows SDK. At the time of this writing, the latest version is the "Windows SDK for Windows Server 2008 and .NET Framework 3.5". Install it to C:\dev\WinSDK

Microsoft DirectX SDK

Go to and download the latest SDK. Install it to c:\dev\DXSDK\


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

Checkout the SVN of WinDBus from to c:\dev\windbus

From download iconv, libxml and zlib. Unpack them to 'c:\Program Files\win32libs'

Run this command:

cd \dev\windbus
patch -p0 < DBus-win32.patch

Now, you'll need to edit some of the files.

Edit windbus\dbus\dbus-spawn-win.c. On line 231, change

sitter->end_sync_event = NULL;


sitter->start_sync_event = NULL;

Edit windbus\dbus\dbus-sysdeps-win.c. On line 3019, change

if(CreateProcessA(dbus_exe_path, dbus_args, NULL, NULL, FALSE, 0, NULL, NULL, &si, &pi))


if(CreateProcessA(dbus_exe_path, dbus_args, NULL, NULL, FALSE, CREATE_NO_WINDOW, NULL, NULL, &si, &pi))

... and then finally, run these commands:

cd \dev
mkdir windbus-build
cd windbus-build
make install

Regardless of what you say, Windbus is installed to c:\<Program Files>\dbus. Move that entire directory into c:\dev (so it ends up as c:\dev\dbus)

Copy all .dll files from c:\Program Files\win32libs\bin to c:\dev\dbus\bin


Download the latest OpenSSL source, unpack it to c:\dev\ (it will create a directory called openssl-x.y.z)

Download and install ActivePerl.

Open a new shell (so that %PATH% includes ActivePerl).

cd \dev
cd openssl-x.y.z
perl Configure VC-WIN32 --prefix=c:\\dev\\OpenSSL
nmake -f ms\ntdll.mak
nmake -f ms\ntdll.mak install

You can remove c:\dev\openssl-x.y.z after this.


Download and unzip to C:\dev. Rename the directory from qt-win-opensource-src-4.3.4 to Qt4.3.4


cd \dev
cd Qt4.3.4
patch -p0 < path/to/qt434.patch
configure -debug-and-release -qt-sql-sqlite -no-qt3support -no-exceptions -qt-zlib -qt-libpng -qt-libjpeg -openssl -qdbus -I c:\dev\openssl\outinc -L c:\dev\openssl\out -I c:\dev\dbus\include -L c:\dev\dbus\lib

This will also take quite a while.

Building Mumble and Murmur

Once all of the above is done... Open C:\dev\mumble\src\mumble\ and remove the line which says CONFIG += asio. That is only needed for ASIO support, which requires downloads of proprietary ASIO SDK to compile.

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 make release instead, which will result in a much smaller binary with fewer dependencies.

cd \dev\mumble
make clean