Tracking Dependencies

Overview

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

Compilers

For C++11 features, see C++11

Libs

C++ bindings are not included, since their required versions match those of the C counterparts.

Library	v 0.91	trunk	trunk (GTK+ 3.0 build)
Boehm-GC	7.1	7.1	7.1
Cairo	1.10	1.10	1.10
GDL	N/A	N/A	3.3.4
Glib	2.28	2.28	2.28
GTK+	2.24	2.24	3.2
GNU Scientific Library	?	?	?
LittleCMS	1.13	1.13	1.13
libxml	2.6.11*	2.6.11*	2.6.11*
libxslt	1.0.15*	1.0.15*	1.0.15*
Pango	?	?	1.24
Poppler	0.5.9*	0.8.3	0.8.3
libsigc++	2.0.12*	2.0.12*	2.0.12*

* Tentative dependency

Distros

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

"Inkscape" column is default or distro version / oldest that builds - latest that builds. If no latest is given then that means trunk is expected to build on the given platform.

e.g. for a distro that ships with 0.48 but should support building of trunk you might get:

0.48 / 0.47-

Distro	Inkscape	gcc	clang	cairo	cairomm	glib	glibmm	gtk+	gtkmm	pango	poppler	gdl	lcms	libsigc++	libgc
Windows Devlibs (32bit) [1] (r53)				1.11.2	1.10.0	2.28.8	2.28.2	2.24.10	2.24.2	1.28.3	0.39.0	(none)	1.17 2.4	2.2.11	7.4.2
Windows Devlibs Gtk+ 3 branch [2] (r34)				1.10.2	1.10.0	2.38.0	2.36.0	2.24.18 3.8.1	2.24.2 3.8.0	1.34.0	0.22.5	3.4.2	1.19 2.4	2.2.10	7.2d
Windows Devlibs 64bit [3] (r17)				1.14.1	1.11.2	2.40.0	2.40.0	2.24.23 3.13.1	2.24.4 3.12.0	1.36.3	0.24.2	3.12.0	- 2.6	2.3.1	7.2
Debian 8.2.0 (Jessie, stable)	0.48.5	4.9.2	3.5	1.14.0	1.10.0	2.42.1	2.42.0	2.24.25 3.14.5	2.24.4 3.14.0	1.36.8	0.26.5	3.14.0	2.6	2.4.0	7.2d
RHEL / CentOS / Scientific Linux 6.x	0.47	4.4.7	X	1.8.8	1.8.0	2.28.8	2.22	2.24.23	2.18.2	1.28.1	0.12.4	X	1.19	2.2.4.2	7.1
RHEL / CentOS / Scientific Linux 7.x	0.48	4.8.3	X	1.12.14	1.10.0	2.40.0	2.36.2	2.24.22 3.8.8	2.24.2 3.8.1	1.34.1	0.22.5	X	2.5.4	2.3.1	7.2d
Ubuntu 12.04 LTS (Precise) EOL 2017-04	0.48.3	4.6.3	(U 3.4)	1.10.2	1.10.0	2.32.4	2.32.0	2.24.10 3.4.2	2.24.2 3.4.0	1.30.0	Getting and Installing Source packages If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download source packages and build and install them yourself. Actually this is not that hard, and is similar to doing a Gentoo 'emerge.' Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with $ tar zxf somepackage-1.0.tar.gz or $ tar jxf somepackage-1.0.tar.bz2 Then 'cd' into the new directory. Configure it with the command: $ ./configure Build it with: $ make As the 'root' user, install it with: # make install Boehm-GC Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source Download this file: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz Unpack it tar zxf gc6.8.tar.gz Configure and build it cd gc6.8 ./configure --disable-shared --enable-static make Install it su (or however else you become root) make install Binaries: If searching for a package for GC, the name of it is sometimes: gc libgc gc-devel libgc-devel boehm-gc (on Gentoo) debian/ubuntu: sudo apt-get install libgc-dev libSigc++ Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2 With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to build this C++ library statically. This removes a dependency that might be difficult for an end-user during installation. Configure it with: ./configure --enable-static --disable-shared GlibMM Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2. Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/ GtkMM Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases. Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2 cairomm if you got prompted about cairomm, try first solve your cairo version, so you can grab there a compatible version. Boost Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it: ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost Source: http://www.boost.org/users/download/ Poppler Source: http://poppler.freedesktop.org/ Poppler is required for PDF import. There are several potential issues: Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See this wishlist bug. This typically manifests in error messages like this: In file included from extension/internal/pdfinput/svg-builder.cpp:19: extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory ... make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1 make[2]: Leaving directory `/tmp/build/inkscape-0.46/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/build/inkscape-0.46' make: *** [all] Error 2 Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See the bug report for details and a minimal patch. Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See this bug for more details. Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.