Gimp depends on the following common libraries
- GLib – a library used by many gnome applications, containing utilities and common data structures for programs written in C.
- GObject - a library for implemnting objects (as in Object-Oriented-Programming) in C.
- GTK+ – a graphical toolkit for building cross-platform user interfaces.
- Cairo – a 2D graphics library, used for drawing some of GIMP’s widget and also used by Gtk+.
GIMP depends on two libraries which are mainly (but not only) intended to be used with GIMP:
- GEGL – a graph based image processing library, heavily used in GIMP’s core.
- babl – a library for converting between pixel formats, heavily used by GIMP when communicating with GEGL.
Some of GIMP's plugins depend on (at least) the following libraries
- librsvg – a library for rendering SVG (Scalable Vector Graphics) files.
- libpng – a library for reading and writing PNG (Portable Network Graphics) image files. Used by Gtk+, GIMP and GEGL.
- libexif - a library for manipulating exif data (image metadata).
- libwmf - a library for working with wmf files.
- libtiff - a library for reading and writing TIFF image files.
- libjpeg - a library for reading and writing JPEG image files.
- liblcms - the Little Color Management System, a library for working with color profiles.
Building from a Tarball vs. building from latest source (Git)
There are 2 types of build we can do:
- A build from Tarball - Tarballs (or in short, TARs) are files which pack together many folders and files, and the term of building from a Tarball refers to building from a package of code that you download from the program's website, for an official release of the program
- A build from Git - The latest source of programs is hosted in a version control system (in our case, the version control is called Git) and you can download the updated source directly from these. The source there is the most up-to-date, and it's sometimes unstable.
It matters to us, in the fact that building from Git requries an additional step (detailed below) and it usually requires more tools. === The build process GIMP, together with GEGL and babl, all use the Gnu build system. This means that compiling them consists of 4 steps:
- autogen.sh script - This script generates the ./configure script for the next step
- In many cases, the autogen script also runs the configure script (see the next step) so we can usually pass arguments to it that will be passed to the configure script.
- This step is only needed when not building from a Tarball!
- configure script - This script does many checks to check which compilers and libraries you have available, which features are enabled and not, etc. When it finishes, it generates the Makefile's which are used by the make tool.
- Usually you can see all the options that you can specify to the script, by running
- One option that we'll use through all of the building tutorials, is the --prefix option
- The path given there is used to specify where do we want the compiled result to be installed to. This is useful when you want to install to places other than the default, for example when we are doing beta-builds and we don't want them to conflict with our existing installation. This can also be used on Linux/Unix system to install into the home-directory, in cases one does not have root access.
- make - The make tool uses files called Makefile, which are present at each directory, in order to call the compilers and other tools and use them on the apropriate source files
- We can speed up the process by running several jobs at once (this is useful when we have a processor with several cores). For example, if we want to run 4 jobs at once, we'll do
- Now, we finally install the compiled result by invoking the make tool again, with the "install" target