The main GIMP building instructions are at Hacking:Building. This page is for Linux-specific additions to that page.
GIMP depends on a lot of other packages in addition to babl, gegl, libmypaint and mypaint-brushes. The requirements change frequently, but on a freshly installed Ubuntu 19.10 system in October 2019, this was enough for most of GIMP's dependencies (there are still a few missing formats, but it builds):
sudo apt install libtool intltool libjson-c-dev meson python3-venv \ python3-wheel cmake liblcms2-dev librsvg2-bin w3m libgtk2.0-dev \ gobject-introspection libjson-glib-dev libgirepository1.0-dev asciidoc \ ruby exiv2 libgexiv2-dev jasper liblensfun-dev libjpeg-dev \ libraw-dev librsvg2-dev libspiro-dev libtiff-dev libv4l-dev luajit \ libopenexr-dev libsdl2-dev libwebp-dev python-gi-dev libavcodec-dev \ libavformat-dev libavutil-dev libswscale-dev libumfpack5 libgtk-3-dev \ libbz2-dev libappstream-glib-dev libarchive-dev gtk-3-examples gjs \ libpoppler-glib-dev xsltproc gtk-doc-tools libaa1-dev \ libwebkit2gtk-4.0-dev libgudev-1.0-dev libwebkit2gtk-4.0-dev libgs-dev \ libopenjp2-7-dev libmng-dev libheif-dev
Running Your Compiled Version of GIMP
You've been through Hacking:Building and finished your build successfully. How do you run it, given that all the programs and libraries are in your special build prefix?
The easiest way is to use a script like this one:
#! /bin/sh # set the path to the installation directory if it isn't already set # in your environment. # export GIMP_PREFIX=/path/to/your/prefix # set the path to the directory into which we download the sources export SRC_DIR=$SRC_DIR # Now, set mandatory enviroment variables export PATH=$GIMP_PREFIX/bin:$PATH export LD_LIBRARY_PATH=$GIMP_PREFIX/lib:$LD_LIBRARY_PATH echo LD_LIBRARY_PATH is $LD_LIBRARY_PATH # Not needed for running GIMP directly, but needed if you want to compile anything against our # builds (think of plug-ins, etc.) export PKG_CONFIG_PATH=$GIMP_PREFIX/lib/pkgconfig:$PKG_CONFIG_PATH # Now you can run executables our other stuff depending on our environment # Here we run GIMP, and pass it any arguments given to this script $GIMP_PREFIX/bin/gimp-2.10 $@
This command creates a shell script that sets some required environment variables and then runs GIMP. Note: If you compiled a gimp version other than 2.10, replace the 2.10 with the correct version.
- I’m getting an error about a too low of GTK+/GLib while compiling XXX
- You can either update your version of GTK+/GLib using your system’s package manager, or compile GTK+/GLib from source! Compiling these is done exactly like we compiled babl – download the source (either the latest from Git, or a package from the official site), compile and install. You may also need to do something like this to a library called ATK.
- I’m getting some error about relative path in the prefix
- The installation directory of libraries/executables must be specified in an absolute path and not in a relative path. If you got this error, it means that one of the paths in your environment variables is relative and not absolute – fix that!
- I'm getting errors about missing/old version of Gtk+/Glib/etc.
- The 3/4 step process described in Hacking:Building for building should work for building most if not all of GIMP's dependancies. Like we compiled GIMP, you should download the sources, run configure then make and finally make install. Use Google or some other search engine to find the website of the package and download it's source from it. Of course that if possible, you should try to install these dependencies through your system's package manager (if you have root permissions) and by that you'll save the time and effort of the compilation.
For other problems, see: Hacking:Problems and solutions
Building the Documentation
To build the documentation
git clone --depth=0 firstname.lastname@example.org:GNOME/gimp-help.git cd gimp-help ./autogen.sh [--without-gimp ALL_LINGUAS="en"] LINGUAS=en make LINGUAS=en make pdf-local
Substitute your language options in the above.
The production of the documentation requires docbook and ancillary programs. Here are some of the other programs;
Which may or may not already installed. Running autogen will stop at the failed dependency, so install and repeat the process till autogen finishes.
It is recommended that you read the README.