Basic Installation
Requirements
- A Linux or FreeBSD compatible operating system.
- At least the Qt 3.3*
development library.
- At least the Berkeley DB 4.1
database. FreeBSD users will have to use the 4.2 version due to compile
issues and package availability.
Installing from source
For Linux users:
- Check to make sure you have your shell QTDIR environment variable
set to point to the location of the root Qt directory. This setting is
usually something like this: 'export QTDIR=/usr/lib/qt' or something
similar to this. Failure to set this properly will result in make
errors.
- Unpack the Qtstalker source.
- ./configure (this will create the Makefile)
- make
- make install (as root)
- the executable 'qtstalker' will be copied to the /usr/bin
directory
- the plugins will be copied to /usr/lib/qtstalker directory
- the docs will be copied to /usr/share/doc/qtstalker/html
directory (toc.html for the table of contents)
- the translation files will be copied to
/usr/share/qtstalker/i18n directory
- Thats it.
For FreeBSD users:
- We have to set a few environment variables first in your shell.
Enter this 'export QTDIR=/usr/X11R6' Then enter this 'export
QMAKESPEC=/usr/local/share/qt/mkspecs/freebsd-g++' . Failure to set
these variables properly will result in make
errors.
- Unpack the Qtstalker source.
- ./configure (this will create the Makefile)
- make
- make install (as root)
- the executable 'qtstalker' will be copied to the /usr/bin
directory
- the plugins will be copied to /usr/lib/qtstalker directory
- the docs will be copied to /usr/share/doc/qtstalker/html
directory (toc.html for the table of contents)
- the translation files will be copied to
/usr/share/qtstalker/i18n directory
- Thats it.
Binary package users can ignore this advice as this will be done
automatically by the package installer.
Updating a previous version.
If you are updating from a previous source version already installed on
your system, it is best
that you first uninstall the previous version first before you install
the upgraded version. Doing this will better ensure a problem-free
upgrade. Many upgrade errors can be caused by old plugins and libraries
hanging around complicating things. You can uninstall the old version
by doing a 'make uninstall' from the root directory of the old source
install.
Using the current development source.
See instructions for using CVS.
