cadManiac.org
    navigation
>projects
   KontrollerLab
>login
    KontrollerLab
>info page
>download
>release schedule
>documentation
  introduction
  installation
  first steps
  compiler settings
  linker settings
  assembler settings
  programmer settings
  debugger
    first steps
    configuration
    direct memory debugger
    PC only debugger
    in circuit debugger
  wizards
    seven segments wizards
    dot matrix library wizard
    dot matrix character wizard
    font wizard
>examples
  font wizard tutorial
hosted by
SourceForge.net Logo
    news
>New site up and running
>New project launched:
KontrollerLab
    information
>propose new project
>bugtracking
>FAQ
>contact
>legal disclaimer
>Not logged in.
    KontrollerLab 

Installation

The installation can be done in three ways (at the moment): We plan to set up a YUM repository to make it easier to keep track of new versions. This repository should be up and running in a few weeks.

If You have problems building the program from the source tarball or from the SVN repository, please have a look at the troubleshooting section.

Building the program from a source package

To build the project from the sources, all You need is the current source tarball (ending of the filename is .tar.bz2 or .tar.gz, respectively), and an up-to-date GNU C++ compiler, which comes with most distributions.
Download a source tarball from our download section or from sourceforge.net. Save it to a local directory, let's say for simplicity, to /home/user/.
Now, extract the tarball.
  • If You have chosen the .tar.gz file, type:
    cd /home/user
    tar xzfv kontrollerlab*.tar.gz
  • If You have chosen the .tar.bz2 file, type:
    cd /home/user
    tar xjfv kontrollerlab*.tar.bz2
Now, there should be a directory, named kontrollerlab-versionnumber.
Enter this directory and configure the sources:
cd kontrollerlab-*
./configure
 The configuration may take a while. Afterwards, compile the source code, using the make command:
make
 If You have more than one processor, You can speed up the compilation by typing make -j3
 which starts 3 compiler jobs simultaneously. In general, it's good to start one more job than there are processors.
When everything went well so far, install the program. You have to be root to do this globally in Your system. (To become root, type su and enter the root password first.):
make install
 Now, the program is ready to use. Start it like this:
kontrollerlab

Building the program from the most recent sources in the SVN repository

First of all, ensure that the subversion tool is installed on your system. You will need it to execute the command svn.

Then, download the most recent sources using this line (there should be no line break in the following command):
svn co https://kontrollerlab.svn.sourceforge.net/svnroot/kontrollerlab/branches/kde3 kontrollerlab
 The sources will now be downloaded and copied to a directory named kontrollerlab in your current working directory. The build process is slightly different from the one which is needed when using a source package. First, You need to create the makefiles:
cd kontrollerlab
make -f Makefile.cvs
 Then, configure the sources, and compile them:
./configure
make
 If You have more than one processor, it is usually a good idea to tell make to start more than one compiler process. In that case, append -j3 to the make command to start 3 processes. One more than the number of processors is a good choice.
Finally, install the tool:
make install
 That's all. You can now start the tool like that:
kontrollerlab

Installing the program as RPM

CURRENTLY THERE IS ONLY RPM SUPPORT FOR FEDORA CORE.
Download the most recent RPM for your distribution in the download section, and save it to, for example, /home/user. Then, become root (Type su and enter the root password first.) and type:
rpm -iv /home/user/kontrollerlab*.rpm
 You can start the KontrollerLab by typing kontrollerlab in a shell.

Installing the program as Ubuntu package

Download the most recent Ubuntu package for your distribution in the download section, and save it to, for example, /home/user. Then type:
sudo dpkg -i /home/user/kontrollerlab*.deb
 You can start the KontrollerLab from the menu or by typing kontrollerlab in a shell.

Installing the program as Debian (Sid) package

Caution: The debian packages are built from the SVN directly and may be unstable or some features may lead to crashes! Anyway, using these packages, You are running one of the latest development snapshots!
Download the most recent Debian package in the download section, and save it to, for example, /home/user. Then type:
sudo dpkg -i /home/user/kontrollerlab*.deb
 If errors occur, You may type
apt-get install -f
to fix the dependencies.
You can start the KontrollerLab from the menu or by typing kontrollerlab in a shell.

Installing the program as Gentoo EBuild

It is possible to install the KontrollerLab as EBuild for Gentoo. More information can be found here:
http://bugs.gentoo.org/show_bug.cgi?id=162116

Installing the program for Arch Linux

This will come soon [07/06/07]

Troubleshooting

In this section You may find problems which may occur during the installation process. Also, the reasons as well as possible solutions are listed here.

Installation on SuSE 10.3

Some users have reported that there is a problem with installing KontrollerLab on SuSE 10.3. This problem can be solved by changing the ./configure command. Use the following line instead of ./configure, the rest remains the same:
KDEDIR=/opt/kde3/lib64 ./configure --with-qt-libraries=/usr/lib64/qt3/lib64 --with-qt-includes=/usr/lib64/qt3/include --prefix=/opt/kde3
Make sure that the code right above is one (1) single line, no linebreaks must be in between when You pass it to a shell!

Qt (>= Qt 3.2) (headers and libraries) not found. Please check your installation!

In this case, there are no QT headers or libraries installed on Your system. Check, if You have a qt-devel package installed (depending on the distribution You use, the name may vary). The second reason may be that the configure script is unable to find the libraries. Check if libtool is installed.
Alternatively, it may help to specify the QT directory directly using a configure flag. For example, when QT is installed to /usr/lib/qt-3.3, try:
./configure --with-qt-dir=/usr/lib/qt-3.3

In the prefix, you've chosen, are no KDE headers installed. This will fail.
So, check this please and use another prefix!

Check if the kdelibs-devel package (depending on the distribution You use, the name may vary) is installed on Your system. The second reason may be that the configure script is unable to find the libraries. Check if libtool is installed.
This site was created using free software only:
The GIMP, Quanta, KPovModeler and Povray.
©2006 cadManiac.org