KIN DB 2004 Project - KinGUI Installation Hints
Project hosted at:
These are simple instructions to install the KinGUI application.
This is not intended as a comprehensive manual, but as
a "quick guide" with basic common procedures and ideas.
For Win32 target (compiling for Windows, both natively -from Windows itself- or cross compiling -from Linux, for an instace-), please see win32 installation section.
Note on updating sources: sometimes a source file is removed from version to version (or renamed), and a remaining object file in your system may lead you to get "duplicate" function definitions (as may be present in both old and new object files). If you find any trouble with an update to rebuild, please try make clean from src directory first. Also sometimes a change in a header file is not detected by the rebuild system as such, and some object files may use wrong data, leading to segmentation violations. If that's your case, issue a make clean, then build and install again.
In short, to avoid troubles, just issue a make clean from src directory before trying to compile after a sources update.
Please read INSTALL file present at distribution
SVN download) for complete instructions. This is a (probably successful)
tar zxvf kingui-dev-0.5-alpha.tgz
(use real package file name). If your tar version can't pipe through gzip, first
tar xvf kingui-dev-0.5-alpha.tar
from where you SVN'd (for the first time) or untar'ed.
Defaults are ok for most people, so first, try it with no modifications.
Go to src
directory. Here type
and wait. For the first time, some files may be created (like config.h), then
compilation starts. If lots of errors arise with the first build line (guilib) or when
linking application (kingui one), probably you don't have an usable SDL library or
headers. It is
looked up at /usr/include/SDL and /usr/local/include/SDL, required
parts are main one (SDL.h), image loading library (SDL_image.h) and TrueType
font manager (SDL_ttf.h), often present at main distributions but otherwise you
can download and install from libSDL site.
You will need the dinamic libSDL when executing KinGUI application.
If all goes right, make will end with no errors.
useradd -g kin kin
(default configuration file uses that values for user and group). For development,
usually user and group are set to your user and group, so you don't have to
sudo to root or to kin user every time you install or run it (in such case,
just remember to set User and Group in kingui.cfg to the desired values).
As root, do (this is for kin based user, change to your user if that's your case):
mkdir /usr/local/kingui; chown kin:kin /usr/local/kingui
Then, back to your user or kin user:
to get all the tree created. As this is alpha, you may have to use this again in
some future, so some new directory gets created whenever it is the case after a
sources update. To have a smooth start, you may also create a symbolic link
for the fonts directory, to your site fonts path, often something like:
ln -s /usr/X11R6/lib/X11/fonts /usr/local/kingui/font
This is not necessary if you create that directory and populate it with your
Tools have to be compiled and eventually installed specifically from their own
directories (see below), if you need them. They need main KinGUI library to be
installed first (as we did a few lines ago), when you choosed modularized version,
else, at least, guilib directory has to been made before.
If you found some trouble trying to compile KinGUI, please refer first to the README file
that comes with your distribution or better, from SVN. If anything fails, please
provide me some information as what you did and some piece of the result on your
console, or at least, the message you get, posting at project's
linux-gate.so.1 => (0xffffe000)
libdl.so.2 => /lib/tls/libdl.so.2 (0xb7f10000)
libSDL-1.2.so.0 => /usr/lib/libSDL-1.2.so.0 (0xb7e7d000)
libSDL_image-1.2.so.0 => /usr/lib/libSDL_image-1.2.so.0 (0xb7e62000)
libSDL_ttf-2.0.so.0 => /usr/lib/libSDL_ttf-2.0.so.0 (0xb7e5d000)
libc.so.6 => /lib/tls/libc.so.6 (0xb7d41000)
libm.so.6 => /lib/tls/libm.so.6 (0xb7d1e000)
libvga.so.1 => /usr/lib/libvga.so.1 (0xb7cca000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb7cb8000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb7c4e000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7c3c000)
If some is missing (no path after the => sign), you have to install it before
running the application (or tell your system's dynamic linker where to find it,
These are some commonly implemented make options for this project:
This simply checks and builds dependancies, and object files ("compiles")
Links object files to build an executable or library (where applicable)
Installs linked executables or libraries. First links them if no object files are available.
Deletes all the compilation results (dependancies, object files, and executables/libraries)
Creates the installation dirs (if not already created and have enough privileges)
|Return to home page|