Prior to version 0.6 of gdivelog, plugins supplied by the author had their own source tree. During the work on 0.6 the plugins were merged into the source tree of gdivelog. This was done primarily because the author got off, well... actually... sat down on his fat lazy &%^$ and learned the GNU autotools properly.


  • GNOME, specifically libgnomeui and prerequisites, version 2.10 or greater
  • SQLite version 3.1.2 or greater
  • libbz2 version 1.0.2 or greater

Most Linux distributions either include the above in the base install or have them available in a package repository or similar. Remeber that you will also need the dev, devel or similar package to compile gdivelog.

In addition to the above, if you plan to install the SmartTrak and/or Suunto Dive Manager 2 plugin you will also need:

See MDB Tools below for futher information.

Configure Options


Compile and install all plugins


Compile and install the Citizen Hyperaqualand plugin


Compile and install the Reefnet Sensus Pro plugin


Compile and install the Uwatec Smart plugin. Requires that the kernel supports IrDA - or at least that the irda.h header file is available and can be compiled successfully. Will also install libuwatec.


Compile and install the Uwatec SmartTrak plugin. Requires MDB Tools. Will also install libuwatec.


Compile and install the Suunto Cobra, Mosquito, Spyder, Stinger, Vyper and Vytec plugin


Compile and install the Suunto Dive Manager 2 plugin. Requires MDB Tools.


Enable the dump feature of plugins. The author aims to have most, if not all, plugins to have the feature to dump raw data to a file for debugging, hacking or other purposes. This code is not built by default, but will be if this parameter is specified.


Do not install utils. The only util at the moment is gdivelog-upgrade-divelog. If you are upgrading from 0.5.1 or below, you will need this util to upgrade your divelog(s).


Do not compile or install any code that uses mdbtools... If you really want to be sure.


The dir of the where installation of mdbtools you want to use is installed. This is the same as the --prefix you used to install MDB Tools.

Installing MDB Tools

The version of MDB Tools used with gdivelog versions 0.5.1 or lower will not work with gdivelog 0.6 or later. A CVS version later than 20051109 is required because support for OLE datatypes was not introduced into MDB Tools until late 2005. The SmartTrak plugin now requires support for the OLE data type as dive profile is stored using this type.

libmdbsimple, part of gdivelog was created to allow simple querying of an Access database, including OLE data types, without requiring libmdbsql.

The easiest way to obtain the required version of mdbtools, if not using Ubuntu Dapper, is to use the Ubuntu Dapper source tarball and patch.

Apply the above patch using the below in the root MDB tools source directory.:

$ zcat [patch] | patch -p1 

This will create a debian/patches subdirectory in the MDB Tools source tree. Apply every patch in that directory using patch with either -p0 or -p1 depending on the patch - if you get an error with -p1, try -p0.


$ patch -p1 -i [patch]

Next, execute the folowing commands in the root of the MDB source tree

$ rm -f configure-stamp
$ libtoolize --force --copy
$ aclocal-1.7
$ autoheader2.50
$ automake-1.7 --add-missing --copy
$ autoconf2.50

NOTE: If you do not have the exact versions of autoconf and automake above, you can try using:

$ rm -f configure-stamp
$ libtoolize --force --copy
$ alocal
$ autoheader
$ automake
$ autoconf

Following this is is the normal configure, make make install. However, I would suggest that you install it into another directory e.g. /opt/gdivelog-mdbtools using --prefix on the configure command:

$ ./configure --prefix=/opt/gdivelog-mdbtools
$ make
# make install

Remember that you will probably need to be root or use su or sudo for the make install step.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.