INSTALL
-------

You will need glib/gtk-1.2.10 (package names like glib and glibdev or 
glib-devel, gtk and gtkdev or gtk-devel) and libexpat (package name should be 
expat) to compile xMule.  Also wxWindows-2.4.0 or greater, linked against 
glib/gtk-1.2.10 is needed (package names wxGTK and wxGTK-devel).

I have used GCC 2.95.2, 3.2, and 3.3 to compile xMule, older GCC's probably 
can't handle Microsoft C++ well enough.

You do not need to patch wxWindows anymore. You can do it, but most of the patch
stuff is already moved into the xMule itself so you will not get much benefits 
from patching. So just grab the prebuilt library for your distribution, install 
it and start compiling the xMule :) (Un-Thesis> You must patch wxWindows' 
src/generic/listctrl.cpp and include/listctrl.h before you can statically link 
it to xMule)

Anyway, if you want to patch, here are the instructions:


PATCH INSTRUCTIONS (OPTIONAL)
-----------------------------
Applying the wx-patch:
cd wxGTK-2.4.0 (or wherever you have extracted wxWindows sources)
patch -p0 < wx-patch


HOW TO COMPILE WXWINDOWS
------------------------
Only GTK1 is supported. Don't try GTK2 anymore. wxWindows isn't ready for it.

For GTK1:
./configure  --prefix=/usr --disable-gtk2 --enable-timedate --enable-gui 
--enable-protocol --enable-http --enable-ftp --enable-resources 
--enable-prologio --disable-debug --enable-final --enable-timer --with-gtk 
--disable-profile

After wxwindows has compiled and you have installed it, you can compile xMule.
do "./configure && make" as usual.  If for some reason, wx-config cannot be 
found, use ./configure --with-wx-config=/path/wx-config.  Sometimes it will be
named wxgtk-2.4-config.

To install it as root type "make install". (You don't have to install if you 
don't like to. It will run fine from the source directory too)

Note: If you are using CVS version, you will have to run ./autogen.sh to 
generate configure script.  Automake > 1.5, Autoconf >= 2.57 and Gettext are 
required and the only versions we will support.

And if you want to remote-administer it, you should definitely try VNC (or 
TightVNC). You probably won't get disappointed :)
http://www.realvnc.org/     http://www.tightvnc.org/

If you change the chart colors and want to select a custom color.. be sure to 
press "Add to custom color"-button and select the color from there. Otherwise 
color will not change :). 

ADVANCED OPTIONS
----------------
There are new configure options:
	--enable-optimise
	--enable-profile

With --enable-optimise, -O flag will be added to the compilation options. If not 
given, no optimization will occur. It is currently preferable not to optimise, 
because if xMule crashes, the optimised code will not produce usable stack 
trace.  -O2 is reported to work fine, -O3 will totally crash on start up, don't 
waste your time as of now.

With --enable-profile, -pg flag will be added to the compilation options. xMule 
will then record profiling data in gmon.out, from which one can see where xMule 
spends its time. You probably do not want to turn this on, unless you want to 
help the devs figure out where your CPU time is going :P
