Guile-Gnome will try to build the following wrappers:

  • Gobject, Glib, Atk, Pango, Pangocairo, Gdk, Gdk-Pixbuf, Gtk, Libglade, Libgnome, Libgnomecanvas, Libgnomeui

All wrappers:

  • Autoconf >= 2.61
  • Automake >= 1.12
  • Guile-2.0 >= 2.0.14 or Guile-2.2
  • G-Wrap >= 1.9.15
  • Guile-Cairo >= 1.10
    • Note that at the time we write, Guile-Cairo 1.10 has not been officially released yet, but either you clone its source tree from here...

      Or, if you prefer, you may download the pre-release I made for this purpose, you will find it here: guile-cairo-1.10.0.tar.gz along with its detached GNUPG signature.

  • Guile-Lib >= 0.2.2
    • Strictly speaking, you only need Guile-Lib if you intend to locally build the documentation and/or run make check, Guile-Gnome's test suite, which is recommended but not mandatory.

Specific wrappers:

Here are the dependencies Guile-Gnome will check, during its configure step, in order to decide which wrappers it can build. Some GNU Linux distributions require you to install the corresponding '-dev' packages, not just the core libraries packages.

  • Atk >= 1.12
  • gconf-2.0 >= 2.18
  • glib-2.0 >= 2.10.0
  • gobject-2.0
  • gthread-2.0
  • gdk-pixbuf-2.0 >= 2.10.0
  • gdk-2.0 >= 2.10.0
  • gtk+-2.0 >= 2.10.0
  • libglade-2.0 >= 2.6
  • libgnome-2.0 >= 2.16
  • libgnomecanvas-2.0 >= 2.14
  • libgnomeui-2.0 >= 2.16.0
  • pango >= 1.14
  • pangocairo >= 1.14


Guile-Gnome uses Git for revision control. The most recent sources can be found at Savannah.

There are currently 2 [important] branches: master and devel. Note that unlike Guile's git organization, Guile-Gnome's stable branch is master, developments occur on the devel branch. To clone, configure, compile and install from the master branch:

The above steps ensure you're using Guile-Gnome's bleeding edge stable version. If you wish to participate to developments, checkout the devel branch:

Happy hacking!


  1. During the configure step, Guile-Gnome will list the wrappers it will buid. You have to scroll-up or edit the config.log file and search for 'available wrappers' to see this important feedback

  2. In the above configure step, --prefix=/your/prefix is optional. The default value is /usr/local.

  3. To install Guile-Gnome, you must have write permissions to the following directories:
    • $prefix and its subdirs
    • Guile's global site directory

    You may check Guile's global site directory using:

    • guile -c "(display (%global-site-dir)) (newline)"

    Guile-Gnome's modules will be installed in $prefix/share/guile-gnome-2, and the file gnome-2.scm will be installed in Guile's global site directory.

  4. In case you need to augment Guile's load paths [for your own Guile-Gnome application(s) for example], you can: (a) create/update your personnal ~/.guile file, (b) update Guile's global site located init.scm file or (c) define/update your GUILE_LOAD_PATH shell environment variable.

  5. Like for any other GNU Tool Chain compatible software, you may install the documentation locally using make install-info, make install-html and/or make install-pdf.