GIMP makes use of the Gimp Toolkit ( GTK+) and other libraries that must be installed first. The main site for the latest offical GIMP distribution is but you should consider using one of the mirrors listed on the download page.

libart2 Grab the module libart_lgpl out of GNOME CVS or fetch the tarball from Īfter grabbing the GIMP distribution, you are ready to compile and install.

PangoFT2 a Pango backend that uses FreeType2 (Make sure you have FreeType2 installed before installing Pango).

The GIMP toolkit can be found at GTK+ 2.4.4 also needs the following packages.

A recent version of pkg-config is needed and you can grab them at.That’s what 300,000+ lines of code get you. In general, expect about 3-4 times as long as a Linux kernel 2.2 compile (for GNU/Linux systems of course). On a P4 or Athlon with 256 megs of RAM, a build can take 20-30 minutes. A full GIMP install including all the gimp-data packs can be 20 megs or more.Ī full compile of the stable version takes 1-2 hours on a PPro 200 or K-6 200 with 64 megs of RAM. This will vary depending on architecture of course. Without debugging and with static libs turned off, GIMP can be compiled in 20-30 megs of space. For a full build with debugging, at least 200 megs free is recomended. For the most part, GCC is recommended, but a lot of effort has gone into making GIMP compile with as many compilers as possible.Ī fair amount of disk space is needed too.

Well, it is necessary to have a C compiler and related tools to compile and install the source package. If you need help with the installation of Windows GIMP, see the GIMP for Windows page. Note for Windows Users: This page is for installation help for the Unix version of GIMP.

How to download gimp for windows 10