Guile-CV needs the following software to run:

  • Autoconf >= 2.69
  • Automake >= 1.14
  • Makeinfo >= 6.6
  • Guile >= 2.0.14
  • [allows 2.2, 3.0 (>= 3.0.7)]

  • Guile-Lib >= 0.2.5
  • Vigra >= 1.11.1
  • Note:

    If you manually install Vigra, make sure you pass the cmake ‑DCMAKE_BUILD_TYPE=RELEASE option, which triggers absolutely essential adequate runtime optimization flags.

  • Vigra C >= commit 3351722 - Jan 18, 2022

    Vigra C - a C wrapper [to some of] the Vigra functionality - is currently only available by cloning its source code git repository: there is no release and no versioning scheme either. But no big deal, its home page has an ’Installation’ section which guides you step by step.


    1. Make sure you pass the cmake ‑DCMAKE_BUILD_TYPE=RELEASE option, which triggers absolutely essential adequate runtime optimization flags;
    2. Vigra C says it depends on cmake >= 3.1, but this is only true if you want to build its documentation, probably not the case. Most distribution still have cmake 2.8, if that is your case, you may safely edit /your/path/vigra_c/CMakeLists.txt and downgrade this requirement to the cmake version installed on your machine;
    3. Make sure the directory where has been installed is ’known’, either because it is defined in /etc/, or you set the environment variable LD_LIBRARY_PATH, otherwise Guile won’t find it and configure will report an error.

  • LaTex

    Any modern latex distribution will do, we use TexLive.

    Guile-CV will check that it can find the standalone documentclass, as well as the following packages: inputenc, fontenc, lmodern, xcolor, booktabs, siunitx and iwona.

    Iwona is the font used to create im-histogram headers, legend indices and footers. Note that it could be that it is not part of your ’basic’ LaTex distro, on debian for example, iwona is part of the texlive-fonts-extra package.

Install from the tarball

Here is the latest Guile-CV 0.4.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 Guile-CV!

Install from the source

Guile-CV uses Git for revision control, hosted on Savannah, you may browse the sources repository here.

There are currently 2 [important] branches: master and devel. Guile-CV 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 Guile-CV bleeding edge stable version. If you wish to participate to developments, checkout the devel branch:

Happy hacking!


  1. The default and --prefix install locations for source modules and compiled files (in the absence of --with-guile-site) are:
    • $(datadir)/guile-cv
    • $(libdir)/guile-cv/guile/$(GUILE_EFFECTIVE_VERSION)/site-ccache

    If you pass --with-guile-site, these becomes:

    • the Guile global site directory
    • the Guile site-ccache directory

  2. The configure step reports these locations as the content of the sitedir and siteccachedir variables, respectivelly the source modules and compiled files install locations.

    After installation, you may consult these variables using pkg-config:

    • pkg-config guile-cv-1.0 --variable=sitedir
    • pkg-config guile-cv-1.0 --variable=siteccachedir

  3. To install Guile-CV, 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 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.
  5. Last but not least, Guile-CV comes with a test-suite, which we recommend you to run (especially before reporting bugs):
    • make check