ef045be7fe
Having a separate RELEASE_ID just unnecessarily complicates drafting releases. Plus, now that we are using different build numbers for every new build anyway, a separate release ID is really not necessary. |
||
|---|---|---|
| .. | ||
| build_installer.md | ||
| build_linux.md | ||
| build_macos.md | ||
| build_static.md | ||
| build_windows.md | ||
| cmake_options.md | ||
| common_build_errors.md | ||
| faq.md | ||
| find_build_number.md | ||
| ide_integration.md | ||
| README.md | ||
| setup_visual_studio.md | ||
Build Mumble
A fundamental dependency for building Mumble is git, so make sure you have it installed. If you are new to git, make sure to checkout this guide on git's basics in order to be able to follow the given instructions.
Furthermore Mumble requires a Cpp14-conform compiler.
The first step in building Mumble is to clone this repository via git clone https://github.com/mumble-voip/mumble.git and then going into the cloned
directory and run git submodule update --init --recursive in order to also clone all submodules.
Tip: You can also build a specific version or commit of Mumble.
Then go into the cloned repository and run git submodule update --init --recursive in order to also clone all submodules.
In order to actually build Mumble, you can follow one of the following instruction sets:
Furthermore you might find these helpful as well: