GNOME modules vary in nature, and include everything from system libraries, through to apps and system services. As a result, they vary in terms of which tools are needed to build them, and the relative complexity involved in building each one.
This page provides an overview of the available build tools and methods. It assumes that you are building GNOME using a recent version of a Linux distribution.
Whenever you want to build a module, it is recommended to check their
README files for any module-specific build instructions.
Meson is the standard build system used by GNOME projects. In many cases it is used indirectly through another tool, such as those described below. However, there are occasions when it might be used directly using the
ninja commands, as specified in per-module build guides.
Builder is GNOME’s IDE. It allows building apps with the click of a button. It automatically takes care of any dependencies that are required by the app, and it builds each project in its own isolated environment, so that it won’t interfere with your host system. This makes it an excellent choice for building most GNOME apps.
Toolbx is a tool for creating nicely integrated containers that can be used as development environments without interfering with your host operating system. Toolbx is an appropriate choice when building:
apps that need resources which cannot be accessed from a Flatpak sandbox (such as hardware or certain APIs)
modules that need access to development versions of system services, for example Settings and Initial Setup
See building with Toolbx for more information on how to build GNOME modules using Toolbox as a build environment.
JHBuild is a command line tool which allows building GNOME modules along with any required dependencies. JHBuild also provides an environment in which modules and services can be built and run without interfering with the rest of your system.
JHBuild can be used in the same circumstances as Toolbx.