G-Golf can be obtained from the following archive site http://ftp.gnu.org/gnu/g-golf/. The file will be named g-golf-version.tar.gz. The current version is 0.8.0-rc9, so the file you should grab is:
http://ftp.gnu.org/gnu/g-golf/g-golf-0.8.0-rc9.tar.gz
* Main Dependencies
G-Golf needs the following software to run:
* Test-Suite Dependencies
G-Golf currently needs the following additional software to run its test-suite:
* Examples Dependencies
– Gtk-4.0 examples –
G-Golf currently needs the following additional software to run its Gtk-4.0 examples:
G-Golf actually requires a patched version of guile-cairo that contains
the following new interface (which is not in guile-cairo 1.11.2):
cairo-pointer->context
.
– Adwaita examples –
G-Golf currently needs the following additional software to run its Adw-1 examples:
Assuming you have satisfied the dependencies, open a terminal and proceed with the following steps:
cd <download-path> tar zxf g-golf-0.8.0-rc9.tar.gz cd g-golf-0.8.0-rc9 ./configure [--prefix=/your/prefix] [--with-guile-site] make make install
Happy G-Golf!
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:
git clone git://git.savannah.gnu.org/g-golf.git cd g-golf ./autogen.sh ./configure [--prefix=/your/prefix] [--with-guile-site] make make install
The above steps ensure you’re using G-Golf
bleeding edge stable
version. If you wish to participate to
developments, checkout the devel
branch:
git checkout devel
Happy hacking!
Notes:
default
and --prefix
installation locations for source
modules and compiled files (in the absence of
--with-guile-site
) are:
$(datadir)/g-golf $(libdir)/g-golf/guile/$(GUILE_EFFECTIVE_VERSION)/site-ccache
If you pass --with-guile-site
, these locations become:
Guile global site directory Guile site-ccache directory
sitedir
and siteccachedir
variables.
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
--with-guile-site
, or unless these locations
are already ’known’ by Guile, you will need to define or augment your
GUILE_LOAD_PATH
and GUILE_COMPILED_PATH
environment
variables accordingly (or %load-path
and
%load-compiled-path
at run time if you prefer3 (See Environment Variables and Load Path in
the Guile Reference Manual).
libg-golf.*
library files, in
$(libdir)
. The configure step reports its location as the content
of the libdir
variable, which depends on on the content of the
prefix
and exec_prefix
variables (also reported).
After installation, you may consult these variables using pkg-config:
pkg-config g-golf-1.0 --variable=prefix pkg-config g-golf-1.0 --variable=exec_prefix pkg-config g-golf-1.0 --variable=libdir
$(libdir)
location is already ’known’ by your system,
you will need - to either define or augment your $LD_LIBRARY_PATH
environment variable, or alter the /etc/ld.so.conf (or add a file
in /etc/ld.so.conf.d) and run (as root) ldconfig
, so that
G-Golf finds its libg-golf.*
library files4.
$(prefix)
directory and its subdirs, as well as to both Guile’s
site and site-ccache directories if --with-guile-site
was
passed.
make install-info
, make
install-html
and/or make install-pdf
.
test-suite
, which we recommend you to run
(especially before Reporting Bugs):
make check
./pre-inst-env your-program [arg1 arg2 ...]
In this
case, you may as well decide to either alter your $HOME/.guile
personal file, or, if you are working in a mult-user environmet, you may
also opt for a global configuration. In this case, the file must be
named init.scm and placed it here (evaluate the following
expression in a terminal): guile -c "(display
(%global-site-dir))(newline)"
.
Contact your
administrator if you opt for the second solution but don’t have
write
priviledges on your system.