Releases can be found on SourceForge, and are packaged in a tar.gz package. Direct link is: https://sourceforge.net/project/showfiles.php?group_id=83870&pac....
There is a Git repository, which contains the latest version of Viking. To download it, just launch:
git clone git://git.code.sf.net/p/viking/code
If you were following the old Sourceforge repository location you'll need to point it to the new one above, such as via this command:
git remote set-url origin git://git.code.sf.net/p/viking/code
You can also view the code online. Use the History feature on that page to see the code commit logs.
Individual commits referenced by an SHA Id can be found by entering the SHA in the URL like this:
Search the appropriate tracker list with the SourceForge#ID will find the ticket from the old reference.
Previously SourceForge used to auto redirect these old URLs to the new IDs, but at the time of writing this no longer works:
Potential future code and other on going works can be found here:
The following libraries are necessary to compile Viking 1.6:
Viking can be compiled with gcc or clang.
On Debian/Ubuntu, the source package already contains all the necessary dependencies. If you don't want to install it, the following command will install them:
apt-get install gnome-common libcurl4-gnutls-dev libexpat1-dev libgtk2.0-dev libglib2.0-dev libgps-dev libbz2-dev libmagic-dev libmapnik2-dev libgexiv2-dev gnome-doc-utils docbook-xsl docbook-xml
As of 2011-03-27, for the current git master (release 1.2 onwards) Viking also needs gtk-doc utilities to compile when using the autogen.sh method:
apt-get install gtk-doc-tools scrollkeeper
For openSUSE you will need to install these packages:
gnome-common gnome-utils-devel libcurl-devel libexpat-devel gtk2-devel gpsd-devel libgevix2-devel libbz2-devel libmagic-devel libmapnik2-devel
Windows requires much more manual work to set up a build environment and the necessary dependencies. This is documented in this separate section Windows Build Instructions.
Viking is supported via Mac Ports.
Some extra notes on setting up the environment for Mac OS see here MacOS Builds.
Then follow the standard compiling instructions below.
Builds can be performed without libgps, libmapnik or other features via running ./autogen.sh with the appropriate --disable-FEATURE argument. To see the available options:
Optional but recommended run-time programs:
If you took the source code from a .tar.gz package, please execute the following commands:
tar -xzvf viking-x.y.z.tar.gz cd viking ./configure make sudo make install # if you want to install in /usr/local - need to have root permissions to install
If you took the source from git, you will have to execute before ./configure:
If you want a fast build using all the available CPUs of your computer, then this command should make it so: