This should be simple. For Windows there is a common installer. Double-click on the downloaded glGo-xxx.exe file and follow the instructions.
The Windows build is statically linked to wxWindows, so you don't need to bother about this.
You need OpenGL libraries installed, they are included in the standard installation of Windows 98 and newer (not recommended) or come with your hardware driver. See section Requirements for details.
The glGo installer includes the redistributable OpenAL library published by Creative.
If you chose to install GNU Go together with glGo, you find the gnugo.exe file in the installation folder, and some GNU Go related documentation in the docs folder.
To avoid large downloads when updating, there are patches from each version to the next. These patches will update the last version (and only the last) to the latest. This should save you some download size and getting OpenAL and GNU Go over and over if you have a slow connection.
The selfextracting installer is used with "sh glGo-xxx.sh". You need to be root or use the sudo utility to run it. (I am investigating if this is possible to change as it is not really required to install glGo with root permissions.)
The installer takes the following commandline parameters:
sh glGo-xxx.sh -gui - Install glGo via GUI (default)
sh glGo-xxx.sh -remove - Remove glGo via GUI
sh glGo-xxx.sh -install - Install glGo via commandline interface
sh glGo-xxx.sh -uninstall - Uninstall glGo via commandline interface
It does not matter if you use the GUI or the commandline interface, just a matter of taste. But I like the idea of Linux GUI installers.
The target directory is /opt/glGo and it will create a symlink to /usr/local/bin/glGo. Uninstall scripts are located in the target directory. The user configuration is found in $HOME/.glGo/. Please remove this directory manually after uninstalling.
In any case you require OpenGL libraries installed, they are installed together with your hardware driver. In worst case, install the Mesa libraries for software-only rendering, but this is not recommended
You need the following SDL libraries: libsdl, libsdl_ttf and libsdl_image. They are all available with all major Linux distributions. If you don't have them already installed, get them from your distribution. In case try ldd glGo to check the dependencies.
You need the Python 2.3 runtime library installed.
For the sound system you need either the OpenAL or the SDL_mixer runtime libraries installed. They should be included in every Linux distribution. Unlike Windows, OpenAL is not included in the Linux glGo installer, as it is to be preferred to use your Linux distribution version. If neither libopenal nor libSDL_mixer are available, glGo should still run, but without sound output.
Here are the most importantant dependencies. Nothing special, but you might need to install some library from your distribution.
Optional for sound output:
GNU Go is not included in the Linux installer. Please install it from your distribution, it is included in almost any, or compile it yourself. Make sure the gnugo binary is found in your PATH environment, so glGo will find it. Common locations are /usr/local/bin, /usr/bin or /usr/games/bin.
If you installed glGo in an unusual directory, you can use the “-s” commandline option to point to the shared data directory. Example: glGo -s /home/foobar/myprogs/coolapps/glGo/share. Another possibility is to set the environment variable “GLGO_SHARED_PATH”, for example in bash: export GLGO_SHARED_PATH=/home/foobar/myprogs/coolapps/glGo/share. The “-s” option has higher priority than the environment variable. If neither is given glGo will search for the shared directory in the folder the binary is located, /usr, /usr/local, /opt, $HOME and $HOME/glGo. If no shared directory is found, glGo will fail to start. If you keep the default directories in the installation and don't move files around later, you do not need to worry about this.
The sound libraries (libalsound.so and libsdlsound.so) are located in /opt/glGo/lib. If you really need to move this directory around, you need to tell glGo the location of these libraries, else sound won't work. You can do this by setting the environment LD_LIBRARY_PATH to the new directory.
This assumes you are using an English Windows. On my German Windows 2000 the folder names are slightly different, but generally the locations are the same.
With release 0.0.5 the configuration is not anymore saved into the registry but into a plain textfile.
C:\Program Files\glGo contains the complete installation. There are subfolders containing the documentation, shared data like images, resources and translations, and the HTML help files.
C:\Documents and Settings\username\glGo contains the configuration file glGo.rc and the logfile glGo.log. If you uninstall glGo, please delete this folder manually. As Windows 9x does not know about a Home directory and writes these files into the Windows system directory, uninstalling this sounds a little dangerous to me.
Some registry entries are automatically generated by the installer for the Windows software installation support. These registry entries are not required by glGo during runtime and are only useful for the installer and uninstaller. They will be completely removed in the uninstall process.
To uninstall glGo, please use the provided uninstaller to clean up the registry entry properly.
The default target directory is /opt/glGo and contains the complete installation.
/usr/local/bin/glGo is a symbolic link to /opt/glGo/bin/glGo to make sure the command is found in your PATH environment.
$HOME/.glGo/ contains the user configuration and temporary cached files.
Uninstall scripts are provided and can be found in /opt/glGo/. The user configuration directory $HOME/.glGo/ will be not uninstalled, please manually delete it.