Building libvips from a source tarball

Check the summary at the end of configure carefully.
libvips must have build-essential, pkg-config, glib2.0-dev, and
libxml2-dev.

For the vips8 Python binding, you must have
gobject-introspection, python-gi-dev, and libgirepository1.0-dev.

You'll need the dev packages for the file format support you
want. For basic jpeg and tiff support, you'll need libtiff5-dev,
libjpeg-turbo8-dev, and libgsf-1-dev. See the Dependencies section
below for a full list of the things that libvips can be configured to use.

Dependencies

libvips has to have gettext, glib2.0-dev and libxml2-dev. Other
dependencies are optional, see below.

Optional dependencies

If suitable versions are found, libvips will add support for the following
libraries automatically. See ./configure --help for a set of flags to
control library detection. Packages are generally found with pkg-config,
so make sure that is working.

libtiff, giflib and libjpeg do not usually use pkg-config so libvips looks for
them in the default path and in $prefix. If you have installed your own
versions of these libraries in a different location, libvips will not see
them. Use switches to libvips configure like:

vips8 Python binding

If gobject-introspection, python-gi-dev, and libgirepository1.0-dev are
available, libvips will install the vips8 Python binding.

libjpeg

The IJG JPEG library. Use the -turbo version if you can.

libexif

If available, libvips adds support for EXIF metadata in JPEG files.

giflib

The standard gif loader. If this is not present, vips will try to load gifs
via imagemagick instead.

librsvg

The usual SVG loader. If this is not present, vips will try to load SVGs
via imagemagick instead.

libpoppler

The usual PDF loader. If this is not present, vips will try to load PDFs
via imagemagick instead.

libgsf-1

If available, libvips adds support for creating image pyramids with dzsave.

libtiff

The TIFF library. It needs to be built with support for JPEG and
ZIP compression. 3.4b037 and later are known to be OK.

fftw3

If libvips finds this library, it uses it for fourier transforms.

lcms2, lcms

If present, vips_icc_import(), vips_icc_export() and vips_icc_transform()
are available for transforming images with ICC profiles. If lcms2 is
available it is used in preference to lcms, since it is faster.

Large files

libvips uses the standard autoconf tests to work out how to support
large files (>2GB) on your system. Any reasonably recent unix should
be OK.

libpng

If present, libvips can load and save png files.

ImageMagick, or optionally GraphicsMagick

If available, libvips adds support for loading all libMagick-supported
image file types. Use --with-magickpackage=GraphicsMagick to build against
graphicsmagick instead.

Imagemagick 6.9+ needs to have been built with --with-modules. Most packaged
IMs are, I think, but if you are rolling your own, you'll need to pass
this flag to configure.

If you are going to be using libvips with untrusted images, perhaps in a
web-server, for example, you should consider the security implications of
using a package with such a large attack surface. You might prefer not to
enable Magick support.

pangoft2

If available, libvips adds support for text rendering. You need the
package pangoft2 in pkg-config --list-all.

orc-0.4

If available, vips will accelerate some operations with this run-time
compiler.