Hi!

This is just a template for a kde app. The original version was written by
Janos Farkas, but I have to change it a lot, since there were some big
problems with it. 
I've used t14 from QT-1.2. I hope I didn't break any rules, but I wanted to
show how easy porting is right on a example, that everybody knows.
I droped automake, since so many developers had problems with this. So only
autoconf (version 2.12) is needed.

The rules: -don't hardcode any paths
           -don't hardcode programs
           -use only one subdir named like your app

the features: 

you can use several programs :
	@CC@ for C-compiler
	@CXX@ for C++-compiler (don't use CC!)
	@INSTALL@ for compatible install
	@MOC@ for moc      

you can use several predefined flags :
	@CXXFLAGS@ is set to "-g -Wall" or "-O2 -Wall"
	@LDFLAGS@ is set to "-s" by default for striping
	@all_libraries@ is set to all needed libraries for compiling KDE
	@all_includes@ is set to all needed include paths 
	@LIBSOCKET@ is set to the needed socket libs (for kfm etc.)
	
Don't use QTDIR and KDEDIR, please use @all_includes@ and @all_libraries@
and @prefix@ for installing.

The one and only subdir from your package can easily be ported to kdebase.
I've seen this idea yet on many packages. Since all kde apps will support the
same variables, it should be more easier to put them together. I've done
this job right now for some kde apps, but I can't do it for every app every
time a new release occurs. So please port your app to this template, I will
support everybody in this task. 

You can just work like on a normal Makefile, but you have to rerun 
config.status, when you have changed the Makefile.in to create a new 
Makefile. When you want to release your package, just 'make distclean',
this will remove all files, that are not needed.

Some details may change in the near or far future, but I don't think, the
general way will.

Sorry, for all the problems with kexample-0.2!

Stephan Kulow (coolo@kde.org)
