Different MinGW compiler versions may NOT work. Even if blender compiles, it may not run on startup or fail otherwise. Read below on "Compiler Version" sections for supported compiler versions!
This page will describe how to build Blender from its git source, and SVN precompiled libaries using MinGW with CMake. Firstly download and install:
- MinGW for 32-bit builds or MinGW-w64 for 64-bit builds. See below for supported versions!
- TortoiseSVN, used to download precompiled libraries for Blender and keep them updated.
- git, used to download Blender's source code and keep it updated.
Be sure to enable the command line tools during installation so you can create a .bat file later on.
Be sure to check "Run git from the Windows Command Prompt" on the configuration page, as it add git to the PATH so you can create a .bat file allowing you to update the source code seamlessly later on.
MinGW Compiler Version
Our libraries have been compiled to be compatible with gcc version 4.6 at most. This is the version of MinGW that you will need. If the default MinGW installer comes with a newer version, you can still download older versions from their GCC packages. Be sure to enable C++ Compiler when downloading!
MinGW-w64 Compiler Version
Please be aware that MinGW-w64 support is experimental. It comes in many flavours so it is simply impossible to maintain support for each and every one, since there is no stable release.
The MinGW-w64 version that has been used for libraries and testing can be found here.
To install it, extract the mingw64 folder from the archive to your C:\ drive, or somewhere else in an easy to remember directory. Make note of this directory for use later in this page.
Set up your Repository
Create a folder to store your copy of the Blender source code. This guide will assume your chosen folder is
C:\BlenderDEV. Then use the command-line to download the Blender source code via git and precompiled libraries via SVN.
Note, to get the precompiled libraries you can use the command-line OR TortoiseSVN, no need to do both, however the command-line is relatively easy to do.
Using the Command line
Open the command prompt window by hitting Windows+R, and then typing cmd, or by searching for it in the start menu.
At the command prompt type the following commands:
cd C:\BlenderDEV git clone git://git.blender.org/blender.git cd blender git submodule update --init --recursive git submodule foreach git checkout master git submodule foreach git pull --rebase origin master
This will checkout the source files to blender/
For additional information on using Git with Blender's sources, see: Tools/Git
+ Checkout 32 Bit libraries...
Make sure the current working directory is the top-level Blender dev directory, so
If you plan on building 32-bit binaries with Microsoft VS-2013, checkout the precompiled library files by typing:
svn checkout https://svn.blender.org/svnroot/bf-blender/trunk/lib/windows_vc12 lib/windows_vc12
If building 32-bit binaries with MinGW, type:
svn checkout https://svn.blender.org/svnroot/bf-blender/trunk/lib/mingw32 lib/mingw32
This will checkout the libraries to lib/windows/ or lib/mingw32/ respectively.
+ Checkout 64 Bit libraries...
Make sure the current working directory is the top-level Blender dev directory, so
If you plan on building 64-bit binaries with Microsoft VS-2013, checkout the precompiled library files by typing:
svn checkout https://svn.blender.org/svnroot/bf-blender/trunk/lib/win64_vc12 lib/win64_vc12
Otherwise if building 64-bit binaries with MinGW-w64, type:
svn checkout https://svn.blender.org/svnroot/bf-blender/trunk/lib/mingw64 lib/mingw64
Again, this will check the libraries out in lib/win64/ or lib/mingw64/ respectively.
Under no circumstances should you set the SVN repository for the
C:\BlenderDEV folder, because it could cause major conflicts with the git repository. If you want to update each precompiled library folder with the explorer context menu, you can do so by clicking on the requisite folders under lib/ and going to SVN checkout. After the checkout finishes you will see a revision and are able to close the dialog out.
The only safe folders that you should use this feature on are the following:
+ Safe Folders for 32 Bit libraries...
+ Safe Folders for 64 Bit libraries...
Update your repository
To keep your local Blender source code and precompiled libraries up to date, you will need to do a git and SVN update once in a while. The most convenient way of doing this is to make a batch file containing the necessary commands.
Create this batch (.bat) file in
+ Update 32 Bit libraries...
For Microsoft VS-2013 32-bit:
cd lib\windows_vc12 svn update cd ..\..\blender git pull --rebase git submodule foreach git pull --rebase origin master pause
For MinGW (32-bit):
cd lib\mingw32 svn update cd ..\..\blender git pull --rebase git submodule foreach git pull --rebase origin master pause
+ Update 64 Bit libraries...
For Microsoft VS-2013 64-bit:
cd lib\win64_vc12 svn update cd ..\..\blender git pull --rebase git submodule foreach git pull --rebase origin master pause
cd lib\mingw64 svn update cd ..\..\blender git pull --rebase git submodule foreach git pull --rebase origin master pause
Run this newly created .bat file whenever you want to update.
TortoiseSVN Explorer Menu
If you plan to compile different versions of Blender with different compilers or targets, and need to have more than one of the precompiled libraries, you can update them individually by right clicking on the requsite library under
C:/BlenderDEV/lib/PRECOMPILED-LIB where "PRECOMPILED-LIB" are the following:
Once you right click on the
C:/BlenderDEV/lib/PRECOMPILED-LIB folder you should choose the
SVN Update option. A TortoiseSVN window will appear listing the files that are updating.
Once the process is finished it will print Completed At Revision: xxxxx at the end of the list.
Just click the OK button to dismiss the dialog.
MinGW & Redistribution
MinGW uses a few DLLs deal with runtime libraries so if you bundle builds for others, copy libgcc*.dll and libstdc++*.dll from MinGW/bin next to your new Blender executable. If you build with OpenMP, libgomp.dll will also be needed. This will make the builds usable even for people who don't have MinGW or PATH setup correctly.
Note, MinGW64 should take care of that automatically for you if you use the supported compiler build.
Missing DLL's With MinGW
If you get a popup when configuring CMake or running SCons that says
libgmp-10.dll not found
This is because the DLL MinGW installs is not in the path, resolve this by adding "C:\MinGW\bin" to you're PATH environment variable.
Fail to Initialize with MinGW
If you get this error, installing python may resolve this, even though Blender comes with python.
The application failed to initialize properly (.....) Click on OK to terminate the application.
File too big
MinGW64 & SCons on Windows might error out when compiling debug builds. Solution is to disable libmv (WITH_LIBMV=OFF on cmake, WITH_BF_LIBMV = False on scons) on those builds.
MinGW and Eclipse
Using Scons plugin to import blender as project does not work properly with MinGW (32Bit). Just add another Scons option in the project's plugin settings:
MSBuild error MSB4019
MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not found.
Fail to start release or builds from buildbot
If you've got PYTHONPATH environment variable pointing to an older version of Python, it'll lead to Microsoft Visual C++ runtime library failure. If you've got such kind of error message, check on your environment variables.
SCons Environment Variable problem
If one ore more environment variable contains a value with non-ASCII characters you'll see an error message appear since r34956 (older revision will throw a UnicodeDecodeError exception). It looks like this:
D:\blenderdev\currentsvn>python scons\scons.py BF_CONFIG=graphicall_32b scons: Reading SConscript files ... ================ @@ ABORTING BUILD @@ PROBLEM DETECTED WITH ENVIRONMENT --------------------------------- A problem with one or more environment variable was found Their value contain non-ascii characters. Check the below list and override them locally to be ASCII-clean by doing 'set VARNAME=cleanvalue' on the command-line prior to starting the build process: USERNAME = Näthan TESTVAR = ElNiño
You don't have to change the main environment, it's enough to override the offending variables for the session. You could create a .bat with the overrides, so it's easy to run it whenever you open a new VS command prompt.