Difference between revisions of "BuildingWindows"

From Mumble Wiki
Jump to: navigation, search
m (Download Mumble and submodules)
Line 199: Line 199:
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.
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.
== Collecting the Dependencies ==
== Collecting the Dependencies ==
Line 249: Line 247:
Now drag Mumble.nsi into the window that popped up and the installer should compile.
Now drag Mumble.nsi into the window that popped up and the installer should compile.

Revision as of 23:32, 19 March 2009

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 mumble.pro file as well. 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


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



Download the most recent Git from http://code.google.com/p/msysgit/downloads/list and install it. Make sure you select "Run Git from the Windows Command Prompt".

Visual Studio

You'll need Visual Studio 2008 (or Visual C++ Express Edition) with SP1.

Visual Studio 2008 Professional 90 day trial: http://msdn2.microsoft.com/en-us/vs2008/products/cc268305.aspx

Visual C++ Express Edition: http://www.microsoft.com/express/download/#webInstall (Look at the bottom right corner for "Visual C++ 2008".)

Create the bat file

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

@echo off
SET QTDIR=C:\dev\Qt4.5.0
SET DBUSDIR=C:\dev\dbus
SET MYSQL=c:\dev\mysql
SET ICE=c:\dev\Ice
CALL "%PROGRAMFILES(X86)%\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" x86
) ELSE (
CALL "%PROGRAMFILES%\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" x86
SET PATH=%QTDIR%\bin;%DBUSDIR%\bin;c:\dev\OpenSSL\bin;c:\dev\cmake\bin;%MYSQL%\lib\opt;%ICE%\bin;%PATH%

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

cd \dev

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.


Download the most recent version of TortoiseSVN at http://tortoisesvn.net/downloads and install it. The defaults are fine.

Intel C++ Compiler

Download and install this: http://www.intel.com/cd/software/products/asmo-na/eng/368972.htm

You only need the file libmmd.dll but currently this seems to be the only official place to get it. If the installer fails it should still install the libraries you need for Mumble.


Download the G15 software from here: http://www.logitech.com/index.cfm/434/180&cl=us,en?WT.ac=sc%7Cdownloads%7C%7Cdd and install it.

Now go to C:\Program Files\Logitech\GamePanel Software\LCD Manager\SDK and extract "LCDSDK_3.01.180.zip". Take the folder that has been extracted and rename it to G15SDK. Put this folder into c:\dev.


Download http://prdownloads.sf.net/boost/boost_1_38_0.7z?download and http://prdownloads.sf.net/boost/boost-jam-3.1.17-1-ntx86.zip?download and unzip both to c:\dev

cd \dev 
cd boost_1_38_0
copy ..\boost-jam-3.1.17-1-ntx86\bjam.exe
bjam --toolset=msvc --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_38_0 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 here to download: http://www.microsoft.com/downloads/details.aspx?FamilyId=E6E1C3DF-A74F-4207-8586-711EBE331CDC&displaylang=en . 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

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.

Microsoft DirectX SDK

Go to http://msdn.microsoft.com/directx/sdk/ and download the latest SDK. Install it to c:\dev\DXSDK\


From http://www.winkde.org/pub/kde/ports/win32/repository/win32libs/ download the following archives:

  • zlib*lib.zip
  • zlib*bin.zip
  • iconv*lib.zip
  • iconv*bin.zip
  • libxml2*bin.tar.bz2
  • libxml2*lib.tar.bz2

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 http://www.cmake.org/files/v2.6/cmake-2.6.2-win32-x86.zip and unpack it to c:\dev. Rename the top directory to just 'cmake'.

Checkout the SVN of WinDBus from https://windbus.svn.sourceforge.net/svnroot/windbus/trunk to c:\dev\windbus

cd \dev 
mkdir windbus-build
cd windbus-build
cmake -DCMAKE_BUILD_TYPE=Release -DDBUS_INSTALL_SYSTEM_LIBS=ON -G "NMake Makefiles" c:\dev\windbus\cmake
nmake 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

You can remove the c:\dev\windbus and c:\dev\windbus-build directories at this point.


Download the OpenSSL source named "openssl-0.9.8g.tar.gz" from here http://www.openssl.org/source/. Unpack it to c:\dev\ (it will create a directory called openssl-x.y.z)

Download and install ActivePerl from here: http://www.activestate.com/activeperl/

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

cd \dev
cd openssl<press tab>
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 the latest release of MySQL Server. It can be found here: http://dev.mysql.com/downloads/mysql/5.1.html#win32 (select "Without installer (unzip in C:\)"). Unzip it to c:\dev\MySQL.


Download the latest version of ZeroC ICE from http://www.zeroc.com/download.html and make sure you select the VS2008 version. Install to c:\dev\Ice


Download ftp://ftp.trolltech.com/qt/source/qt-win-opensource-src-4.5.0.zip and unzip to C:\dev. Rename the directory from qt-win-opensource-src-4.5.0 to Qt4.5.0

Download http://mumble.sourceforge.net/qt450msvc.patch and put it in c:\dev\Qt4.5.0. Then, start Git Bash, which came with git.

cd /c/dev/Qt4.5.0
patch -lp0 < qt450msvc.patch

Start a regular command shell:

cd \dev
cd Qt4.5.0
configure -debug-and-release -qt-sql-sqlite -qt-sql-mysql -no-qt3support -no-exceptions -qt-zlib -qt-libpng  -qt-libjpeg  -openssl-linked -dbus-linked -I c:\dev\OpenSSL\include -L c:\dev\OpenSSL\lib -I c:\dev\dbus\include -L c:\dev\dbus\lib -I c:\dev\mysql\include -L c:\dev\mysql\lib\opt -platform win32-msvc2008

This will also take quite a while.


Download http://downloads.xiph.org/releases/ogg/libogg-1.1.3.zip and unpack it to c:\dev\libogg. Use the included project files to build a static library (double click C:\dev\libogg\win32\ogg.dsw and MSVC should start. Select Build -> Batch Build -> check both ogg_static's and then click Build). Two files should be in C:\dev\libogg\win32\Static_Debug and C:\dev\libogg\win32\Static_Release. Take both of these files and put them in c:\dev\libogg\lib then rename the files from ogg_static.lib and ogg_static_d.lib to libogg.lib and libogg_d.lib.

Download Mumble and Submodules

To clone the repositories :

cd \dev
git clone git://mumble.git.sourceforge.net/gitroot/mumble mumble
cd mumble
git submodule init
git submodule update

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. If you do not need it you can disable it by editing the C:\dev\mumble\src\mumble.pri. Add no-asio to the line which says CONFIG += qt thread debug_and_release warn_on to make it CONFIG += qt thread debug_and_release warn_on no-asio. This disables support for ASIO and gets rid of the dependency. If you want to compile Mumble without G15 support change the qmake command below to qmake CONFIG+="no-g15" main.pro

cd \dev
cd mumble
nmake clean

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.

Collecting the Dependencies

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 you do this, however, you need to either manually collect the various libraries Mumble and Murmur need to run or make an NSI installer. To manually collect the files for a release build just look at which files the official NSI installer puts into C:\Program Files\Mumble and do the same for your own compile. The files will be in c:\dev in their respecive folders. For instance the QT files will be in c:\dev\Qt4.5.0.

However, for a debug build a few things are different. If you compiled Mumble exactly as described in the guide, you need to find these files and put them in c:\dev\mumble\debug. The words above the filenames denote the path name from c:\dev.











If you wish to make an NSI installer, download the latest version of NSIS Unicode here:


You also need to download this file, extract it, and put the dll into

"C:\Program Files\NSIS\Unicode\Plugins"


Do the same for FindProcUnicode.dll. You will need to download an official NSIS compiled version of Mumble and open it with 7-zip or some type of archive manager and navigate to $PLUGINSDIR to find this file. Put it in the same place as CPUFeatures.dll.

Start NCIS, and click "Compile NSI scripts"

Note that Mumble.nsi is coded for 64 bit Windows, therefore you need to modify it and remove the (x86) out of the "Program Files" parts of the code. Also, find murmur.ini.win32 and remove ".win32". Now copy all pdb files from the debug folder and put them in the release folder.

Now drag Mumble.nsi into the window that popped up and the installer should compile.