Dependencies

Grip will look for the following dependencies and will try to install all its components, but will only do so if it can effectively install Grip core and statisfy the component specific requirement(s).

If you are only interested by Grip (core), then you only need Guile, and you may safely ignore all other dependencies.

Grip:

  • Autoconf >= 2.69
  • Automake >= 1.14
  • Guile-2.0 >= 2.0.14 or Guile-2.2

  • Guile-Lib >= 0.2.5
    • This is a soft dependency: Guile-Lib is required to run the test-suite, which is recommended but not mandatory.

Grip-SQLite:

Grip-Gnome:

  • Guile-Gnome >= 2.16.5, the following wrappers:
    • Glib, Gobject, Gtk, libglade

Grip-Clutter:

Install from the tarball

The latest release is Grip 0.2.0 release, with its GPG binary signature. Other releases are available here.

Assuming you have satisfied the dependencies, open a terminal and proceed with the following steps:

Happy Grip!

Install from the source

Grip uses Git for revision control. The most recent sources can be found at here.

There are currently 2 [important] branches: master and devel. Grip's stable branch is master, developments occur on the devel branch.

So, to grab, compile and install from the source, open a terminal and:

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

Happy hacking!

Notes

  1. The default and --prefix installation locations for source modules and compiled files (in the absence of --with-guile-site=yes, otherwise see below) are:
    • $(datadir)/grip
    • $(libdir)/grip/guile/$(GUILE_EFFECTIVE_VERSION)/site-ccache

    In the above, $(datadir) is substituted to the default /usr/local/share or /your/prefix/share and $(libdir) is substituted to /usr/local/lib or /your/prefix/lib, when/if --prefix was passed.

    $(GUILE_EFFECTIVE_VERSION) is substituted to the Guile stable version number with which Grip is being compile, for example, 2.2 ...

    Unless you passed --with-guile-site=yes, you must augment Guile's %load-path and %load-compiled-path, respectively, with the two (substituted) paths described above, so that Guile finds Grip's installed source modules and compiled files.

    To do this, you either (a) create/update your personnal ~/.guile file, (b) update Guile's global site init.scm file or (c) define/update (and export) both GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH (Make sure you read Guile's manual 'Environment Variables' and 'Load Paths' subsections if you are not familiar).

    Here is an example for (c), assuming these variables were not already defined and no --prefix has been given, using the Bash shell:

    • export GUILE_LOAD_PATH="/usr/local/share/grip"
    • export GUILE_LOAD_COMPILED_PATH="/usr/local/lib/grip/guile/2.2/site-ccache"
  2. If you pass --with-guile-site=yes, Grip's source modules and compiled files will be installed using Guile's global site and site-ccache directories, respectively. You may check these two locations using:
    • guile -c "(display (%global-site-dir)) (newline)"
    • guile -c "(display (%site-ccache-dir)) (newline)"
  3. To install Grip, you must have write permissions to the default or $prefix dir and its subdirs, as well as to both Guile's global site and site-ccache directories if --with-guile-site=yes was passed.
  4. 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.