G-Golf needs the following software to run:

Install from the tarball

G-Golf is under active development and we hope to be able to release an alpha version within the next few months, but currently, there is no available tarball. If you want to try or just follow G-Golf, consider installing from the source.

Install from the source

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

There are currently 2 [important] branches: master and devel. G-Golf 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 G-Golf bleeding edge stable version. If you wish to participate to G-Golf, 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=yes) are:
    • $(datadir)/g-golf
    • $(libdir)/g-golf/guile/$(GUILE_EFFECTIVE_VERSION)/site-ccache

    If you pass --with-guile-site=yes, 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 g-golf-1.0 --variable=sitedir
    • pkg-config g-golf-1.0 --variable=siteccachedir

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