
Kludge3d requires GTK 2.2.x and gtkglext to work.  If you don't have them, 
then check out the kludge3d web site for links to the gtk and gtkglext 
web sites.

OPTIONAL: If you want to be able to load 3ds files, you need to install lib3ds.
However, lib3ds is optional... if the configure script doesn't find it,
the 3ds stuff gets #ifdef'd out.

OPTIONAL: If you want to be able to run scripts within kludge3d, you'll need 
to install Python.  Python 2.2.x is the version that the configure script will 
look for.  Python is optional.

A NOTE REGARDING PYTHON: If you have Python installed, but do not have the 
Python development headers and the Python C-interface-library installed, you 
will not be able to use the embedded Python feature.  In this situation, you 
should use the '--disable-python' argument when running the configure script.

Once you've got everything installed, compiling kludge3d should go 
something like this:

	./configure
	make

If you don't have gtkgl installed in the standard place (/usr/local/...)
then you might have to specify it's location with the --with-gtkgl-prefix
argument.  Same goes for lib3ds (you'd use --with-lib3ds-prefix).

Just run kludge3d from the src directory, or copy it into your ~/bin 
directory.  Check out the website for usage instructions.

SOME COMMENTS ON THE ~/.kludge3d DIRECTORY:
Kludge3d will automatically create this directory if it does not exist.  
This directory is where your preferences are stored (prefs.txt), and is also 
a convenient place to store your Python scripts.  On startup, kludge3d will 
check to see if you have a file called "base.py" in your ~/.kludge3d directory.
If such a file exists, kludge3d will execute it.  You can use this to 
automatically import your Python modules.  A sample base.py can be found in 
the "scripts" directory.  I would suggest that you copy all of the .py files in 
"scripts" to your ~/.kludge3d directory.


If you're trying to compile kludge3d on windows (which, I've been told, is
possible), you might want to try the makefile.mingw in the src directory.
It may not be up to date...

Write me at ads4260@rit.edu if you need help.


