To get the latest Blender successfully running on Linux system, follow a few simple steps.
- Download Blender source.
- Install required package dependencies.
- Compile Blender.
1. Get the source
The first step is to get the latest Blender source code from blender.org's GIT repository.
Copy and paste the following instructions into a terminal window. The following commands create a blender-git folder in your home directory by downloading the latest source code commonly referred to as 'master'. An Internet connection is needed.
mkdir ~/blender-git cd ~/blender-git git clone https://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
If you want to update your git clone checkout to the latest source do (in ~/blender-git/blender/):
git pull --rebase git submodule foreach git pull --rebase origin master
For additional information on using Git with Blender's sources, see: Tools/Git
2. Install/Update the dependencies
Automatic dependencies installation
The preferred way to install dependencies under Linux is now to use the
script featured with Blender sources.
It currently supports Debian (and derived), Fedora, Suse and Arch distributions.
When using the
install_deps.sh script, you are only required to install the following dependencies:
zypper install git gcc-c++
Then, get the sources and run
cd ~/blender-git ./blender/build_files/build_environment/install_deps.sh
This script works for Debian/Redhat/SuSE/Arch based distributions, both 32 and 64 bits.
For other distributions, it can:
- Print the list of all main dependencies needed to build Blender (
- Attempt to build main 'big' libraries you cannot easily install from packages (
--helpof the script for details).
Some commands in this script requires sudo, so you'll be likely be asked for your password.
When the script finishes installing/building all the packages, it'll print which parameters for CMake and SCons you should use to build Blender.
+ install_deps.sh options
This scripts accepts some optional command lines arguments (use
+ Manual Dependency Installation (optional)
Manual Dependency Installation
To manually install Blender's dependancy packages:
Install Packman repository
zypper addrepo http://packman.jacobs-university.de/suse/11.3/ packman
or use Yast to install Packman repository.
Then install the dependencies:
zypper install mc git gcc-c++ libSDL-devel \ openal-soft-devel libffmpeg-devel \ libpng-devel libjpeg-devel python3-devel libtiff-devel OpenEXR-devel
As a final note, here are the key libraries that you may want to use with Blender:
See also: Building Dependencies From Source
3. Compile Blender with CMake
Install CMake from your package manager.
Automatic CMake Setup
If you're not interested in manually setting up CMake build directory, configuring, building and installing in separate steps, we provide a convenience makefile in Blender's source directory which sets up CMake for you.
cd ~/blender-git/blender make
Once the build finishes you'll get a message like..
Blender successfully built, run from: /home/me/blender-git/build_linux/bin/blender
Updating your local checkout and rebuilding is as simple as:
cd ~/blender-git/blender make update make
There are some pre-defined build targets:
- make - some are turned off by default because they can be difficult to correctly configure for newer developers and aren't essential to use & develop Blender in most cases.
- make lite - the quickest way to get a Blender build up & running, can also help to avoid installing a lot of dependencies if you don't need video-codecs, physics-sim & cycles rendering.
- make full - this makes a complete build with all options enabled, matching the releases on blender.org.
For a full list of the optional targets type...
Manual CMake Setup
+ Manual CMake Setup (optional)
If you want to have more control over your build configuration or have multiple build directories for a single source directory. You can follow these steps.
Typically useful for developers, who built frequently.
Preparing CMake's directory
Now you have to choose a location for CMake build files, currently in-source builds in Blender aren't supported.
By doing an "out-of-source" build you create a CMake's directory aside from
mkdir ~/blender-git/build cd ~/blender-git/build cmake ../blender
This will generate makefiles in the build directory (
Editing CMake Parameters
Note that CMake should detect correct parameters so you shouldn't need change defaults to simply to compile blender, this is only if you want to change defaults, make a debug build, disable features etc,
You can modify the build parameters in different ways:
cmake ../blender \ -DCMAKE_INSTALL_PREFIX=/opt/blender \ -DWITH_INSTALL_PORTABLE=OFF \ -DWITH_BUILDINFO=OFF \ -DWITH_GAMEENGINE=OFF
After changes have been done and you have generated the makefiles, you can compile using the make command inside the build directory:
cd ~/blender-git/build make make install
Also notice the install target is used, this will copy scripts and documentation into ~/blender-git/build/bin
For future builds you can simply update the repository and re-run make.
cd ~/blender-git/blender git pull --rebase git submodule foreach git pull --rebase origin master cd ~/blender-git/build make make install
If you want to share your build with others you may want to include libraries with Blender (statically linked libraries).
Static Linking Each Library:
TODO: other libs?
+ Optimize Rebuilds (optional)
Now that you can build blender and run blender, there are changes you can make which greatly increase the speed of build times.
Use one of the CMake configuration editors (ccmake or cmake-gui), see Editing CMake Parameters
For really fast rebuilds you can disable Every option with the WITH_ prefix, except for WITH_PYTHON which is needed for the UI. This speeds up linking and gives a smaller binary.
Remove the files created by make install since they will become stale. However, blender still needs to be able to find its scripts or you will have a very minimalist looking interface. This can be solved by linking the source directory to your blender binary path so copying isn't needed and scripts are always up to date.
rm -r ~/blender-git/build/bin/*.* ln -s ~/blender-git/blender/release ~/blender-git/build/bin/
For convenient access, create this symlink to run blender from the source directory:
ln -s ~/blender-git/build/bin/blender ~/blender-git/blender/blender.bin
You can add any files created this way to ~/blender-git/blender/.git/info/exclude so they won't count as untracked files for git. Add your local files here, instead of in .gitignore, because .gitignore is also committed and will affect everyone else.
Certificate verification error
If you try to check out your code from a hosted subversion repository, under Ubuntu 10.04 or newer, you may be disappointed to have it fail with the error:
svn: OPTIONS of 'https://server.com/repo': Certificate verification error: signed using insecure algorithm (https://server.com/repo)
In the [groups] section (before [global]) of your ~/.subversion/servers add the following:
blender = svn.blender.org [blender] ssl-trust-default-ca = no