###################################
#                                 #
#     INSTALL file for KBFX       #
#                                 #
###################################
Last update: 18/06/2006

Installation Notes by PhobosK



1. Requirements :
=================

- automake
- KDE and QT sources - header files/devel packages




2. Compilation Instructions :
=============================

 2.1. Unpack the sources of KBFX with (x.y.z represents the version of
      package, for example : 0.4.9):

    > tar xzvf kbfx-x.y.z.tar.gz

 2.2. Change into the new directory:

    > cd kbfx-x.y.z/

 2.3. Generate the necessary files for the compilation using the command:
 
    > ./autogen.sh
	
	OR (for KBFX versions <= 0.4.9.1):
	
    > make -f Makefile.cvs

 2.4. Configure, compile and install the program by:

    > ./configure --prefix=`kde-config --prefix`
    > make
    > su
    > make install

	Note for Mandriva users for KBFX versions > 0.4.9.1 :
	======================================================
 
	The configure script (by default) enables the use of "menudrake"
	instead of "kmenuedit". If you want to prevent this behavior then
	pass the option:
	"--disable-menudrake" to the configure script.
 
	Additional options for the configure script for versions > 0.4.9.1 :
	====================================================================
	
	--enable-debuglog - This option enables the creation of the
			    '$HOME/.kbfxlogfile' debug log file for the
			    KBFX Application (default = no debug
			    log file)
 
 2.5. You may now run the configuration program by typing "kbfxconfigapp",
      or start the program by selecting and adding the "KBFX Spinx X.Y.Z"
      Applet to one of the KDE Pannels. For more info see the HOWTO file.

	
	Notes for KBFX versions <= 0.4.9.1 :
	====================================

	- Workaround for Suse and Gentoo:
	Since these distributions do not install KDE in /usr ld linker does
	not pick up libkio. So:
		1. Download automake 1.6 and install
		2. Run "kde-config --prefix" and find out where your
		   KDE prefix is
		3. Given your KDE prefix is /opt/kde3/:
			Open kbfxconfigapp/Makefile.am
			Replace $(LIB_KIO) with -L/opt/kde3/lib/ -lkio
		4. Compile as normal

	Notes for KBFX versions > 0.4.9.1 :
	===================================

	- Follow the compilation instructions 2.1 and 2.2.
	- Next you can run the script "build.sh" to configure and make KBFX:
		> ./build.sh
	- Now you can install KBFX by:
		> su
		> make install
	- Follow the compilation instructions 2.5.

	Notes for KBFX CVS versions :
	=============================

	- Follow the compilation instructions described in "Notes for
	  KBFX versions  > 0.4.9.1".
	
	


3. RPM Building Instructions (Mandriva, Fedora, Suse) :
=======================================================

If you prefer manipulate a RPM, you can build it with the following commands:

 3.1. Build the RPM

    > rpmbuild -tb kbfx-x.y.z.tar.gz

   or (for Mandriva)

    > rpmbuild --rebuild kbfx-x.y.z-mdk2006.src.rpm
   
   or (for Fedora)
   
    > rpmbuild --rebuild kbfx-x.y.z-FCx.src.rpm

 3.2. If succeed, you will found the rpm in /usr/src/RPM/RPMS (for Mandriva)
      or /usr/src/redhat/RPMS (for Fedora) according to the platform
      you have.

 3.3. Install the rpm as usually by:
    > rpm -Uvh kbfx-x.y.z.rpm

	Notes for building RPM from KBFX CVS versions :
	===============================================

	- Follow these commands in the sources directory:
		> ./autogen.sh
		> ./configure --prefix=`kde-config --prefix`
		> make dist
	- A file "kbfx-x.y.z.tar.gz" will be created in the sources
	  directory.
	- Proceed with the steps described in 3.1., 3.2., 3.3.


4. Getting CVS version:
=======================

To download the latest development source, you need to go to cvs
and download it there. 
Here are the instructions on how to get a copy of the CVS Repository
by anonymous CVS access: 

 cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/kbfx login

 cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/kbfx co modulename

The modulename with the current source files of the development version
of KBFX is "kbfxwork"
The modulename with the current source files of the stable version of
KBFX is "kbfxstable"
 
If you want to see the current status of the source files of KBFX,
you may browse the CVS Repository of the Project here:
	http://cvs.savannah.nongnu.org/viewcvs/?root=kbfx






=======================================================
General Configure and Installation Instructions follow:
=======================================================


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 a while.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package.

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

  4. You can remove the program binaries and object files from the
     source code directory by typing `make clean'.

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.

   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.

