*****************************************
*                    *
*        knoda          *
*       INSTALL         *
*                    *
*****************************************


=========
CONTENTS
=========
1. SOFTWARE REQUIREMENTS
2. KNODA CONFIGURATION OPTIONS
3. CONFIGURATION
4. BUILDING THE PROGRAMM
5. IMPORTANT
6. Basic Installation


=========================
1. SOFTWARE REQUIREMENTS
=========================


* hk_classes
* KDE3
* qt3


==============================
2. KNODA CONFIGURATION OPTIONS
==============================

Usage: ./configure [OPTION]... [VAR=VALUE]...

Examples:
Redhat, Debian, Mandrake: ./configure --prefix=/usr
Suse: ./configure  --prefix=/opt/kde3




To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
 -h, --help       display this help and exit
   --help=short    display options specific to this package
   --help=recursive  display the short help of all the included packages
 -V, --version      display version information and exit
 -q, --quiet, --silent  do not print `checking...' messages
   --cache-file=FILE  cache test results in FILE [disabled]
 -C, --config-cache   alias for `--cache-file=config.cache'
 -n, --no-create     do not create output files
   --srcdir=DIR    find the sources in DIR [configure dir or `..']

Installation directories:
 --prefix=PREFIX     install architecture-independent files in PREFIX
             [/opt/kde3]
 --exec-prefix=EPREFIX  install architecture-dependent files in EPREFIX
             [PREFIX]

By default, `make install' will install all the files in
`/opt/kde3/bin', `/opt/kde3/lib' etc. You can specify
an installation prefix other than `/opt/kde3' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
 --bindir=DIR      user executables [EPREFIX/bin]
 --sbindir=DIR     system admin executables [EPREFIX/sbin]
 --libexecdir=DIR    program executables [EPREFIX/libexec]
 --datadir=DIR     read-only architecture-independent data [PREFIX/share]
 --sysconfdir=DIR    read-only single-machine data [PREFIX/etc]
 --sharedstatedir=DIR  modifiable architecture-independent data [PREFIX/com]
 --localstatedir=DIR  modifiable single-machine data [PREFIX/var]
 --libdir=DIR      object code libraries [EPREFIX/lib]
 --includedir=DIR    C header files [PREFIX/include]
 --oldincludedir=DIR  C header files for non-gcc [/usr/include]
 --infodir=DIR     info documentation [PREFIX/info]
 --mandir=DIR      man documentation [PREFIX/man]

Program names:
 --program-prefix=PREFIX      prepend PREFIX to installed program names
 --program-suffix=SUFFIX      append SUFFIX to installed program names
 --program-transform-name=PROGRAM  run sed PROGRAM on installed program names

System types:
 --build=BUILD   configure for building on BUILD [guessed]
 --host=HOST    build programs to run on HOST [BUILD]
 --target=TARGET  configure for building compilers for TARGET [HOST]

Optional Features:
 --disable-FEATURE    do not include FEATURE (same as --enable-FEATURE=no)
 --enable-FEATURE[=ARG] include FEATURE [ARG=yes]
 --disable-fast-perl   disable fast Makefile generation (needs perl)
 --enable-debug     enables debug symbols default=no
 --disable-debug     disables debug output and debug symbols default=no
 --enable-strict     compiles with strict compiler options (may not work!)
 --enable-profile    creates profiling infos default=no
 --enable-final     build size optimized apps (experimental - needs lots of memory)
 --disable-closure    don't delay template instantiation
 --enable-shared=PKGS build shared libraries default=yes
 --enable-static=PKGS build static libraries default=no
 --enable-fast-install=PKGS optimize for fast installation default=yes
 --disable-libtool-lock avoid locking (might break parallel builds)
 --enable-embedded    link to Qt-embedded, don't use X
 --disable-mt       link to non-threaded Qt (deprecated)
 --enable-kernel-threads Enable the use of the LinuxThreads port on FreeBSD/i386 only.
 --disable-threading   disables threading even if libpthread found
 --disable-rpath     do not use the rpath feature of ld
 --disable-path-check  don't try to find out, where to install

Optional Packages:
 --with-PACKAGE[=ARG]  use PACKAGE [ARG=yes]
 --without-PACKAGE    do not use PACKAGE (same as --with-PACKAGE=no)
 --with-kde-version=N  KDE version to configure for: 2 (default) or 3
 --with-gnu-ld      assume the C compiler uses GNU ld default=no
 --with-pic       try to use only PIC/non-PIC objects default=use both
  --with-hk_classes-dir=PATH      Path to the hk_classes directory
  --with-hk_classes-incdir=PATH   Path to the hk_classes header files
 --with-xinerama    enable support for Xinerama
 --with-extra-includes=DIR
             adds non standard include paths
 --with-extra-libs=DIR  adds non standard library paths
 --with-qt-dir=DIR    where the root of Qt is installed
 --with-qt-includes=DIR where the Qt includes are.
 --with-qt-libraries=DIR where the Qt library is installed.

Some influential environment variables:
 CC     C compiler command
 CFLAGS   C compiler flags
 LDFLAGS   linker flags, e.g. -L<lib dir> if you have libraries in a
       nonstandard directory <lib dir>
 CPPFLAGS  C/C++ preprocessor flags, e.g. -I<include dir> if you have
       headers in a nonstandard directory <include dir>
 CXX     C++ compiler command
 CXXFLAGS  C++ compiler flags
 CXXCPP   C++ preprocessor
 CPP     C preprocessor

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.

=================
3. CONFIGURATION
=================

# ./configure --with-kde-version=3 --prefix=/your/kde3/path --with-qt-dir=/your/qt3/path

For non-standard hk_classes installation your can use the following parameters:
  --with-hk_classes-dir=PATH      Path to the hk_classes directory
  --with-hk_classes-incdir=PATH   Path to the hk_classes header files


========================
4. BUILDING THE PROGRAMM
========================

once the program is configured, then just execute the
following commands:

# make
# su
# make install


============
5. IMPORTANT
============

add the prefix to configure with the KDE directory as parameter
Suse 7.3 users should add: /opt/kde3
Mandrake users should add: /usr
all other distributions add: the KDE path


=====================================
Horst Knorr <hk_classes@knoda.org>
=====================================








======================================================================
======================================================================
=====================
6. Basic Installation
=====================

 These are generic installation instructions.

 The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

 If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

 The file `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

 1. `cd' to the directory containing the package's source code and type
  `./configure' to configure the package for your system. If you're
  using `csh' on an old version of System V, you might need to type
  `sh ./configure' instead to prevent `csh' from trying to execute
  `configure' itself.

  Running `configure' takes awhile. While running, it prints some
  messages telling which features it is checking for.

 2. Type `make' to compile the package.

 3. Optionally, type `make check' to run any self-tests that come with
  the package.

 4. Type `make install' to install the programs and any data files and
  documentation.

 5. You can remove the program binaries and object files from the
  source code directory by typing `make clean'. To also remove the
  files that `configure' created (so you can compile the package for
  a different kind of computer), type `make distclean'. There is
  also a `make maintainer-clean' target, but that is intended mainly
  for the package's developers. If you use it, you may have to get
  all sorts of other programs in order to regenerate files that came
  with the distribution.

Compilers and Options
=====================

 Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
  CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
  env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures
====================================

 You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

 If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

 By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

 You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

 In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.

 If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

 Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

 For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

 There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
  CPU-COMPANY-SYSTEM

See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.

 If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults
================

 If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Operation Controls
==================

 `configure' recognizes the following options to control how it
operates.

`--cache-file=FILE'
  Use and save the results of the tests in FILE instead of
  `./config.cache'. Set FILE to `/dev/null' to disable caching, for
  debugging `configure'.

`--help'
  Print a summary of the options to `configure', and exit.

`--quiet'
`--silent'
`-q'
  Do not print messages saying which checks are being made.

`--srcdir=DIR'
  Look for the package's source code in directory DIR. Usually
  `configure' can determine that directory automatically.

`--version'
  Print the version of Autoconf used to generate the `configure'
  script, and exit.

`configure' also accepts some other, not widely useful, options.





