Installation Instructions for Building/Installing libDockApp
------------------------------------------------------------


SUPPORTED PLATFORMS
===================
(ie: Window Maker works on these platforms so I'm sure this will do as well)

- Intel GNU/Linux Slackware 3.5 (primary platform)
- Intel GNU/Linux other distributions
- Sparc GNU/Linux RedHat 5.1
- PowerPC GNU/MkLinux
- Alpha GNU/Linux RedHat 5.1
- FreeBSD
- NetBSD
- OpenBSD
- BSDI 4.0
- Solaris 2.5.1, 2.5.2
- Solaris 2.6.0
- Solaris 2.7beta
- SCO Unix
- SGI Irix 5.x, 6.5
- OSF/1
- HP-UX
- AIX 3.2.5
- AIX 4.1.4 / IBM PowerPC
- AIX 4.3.1 / IBM CC compiler
- AIX 4.3.2 / IBM PowerPC
- AIX 5.3
- DEC Alpha/Digital UNIX 4.x
- XFree86 / OS/2
- Corel NetWinder
- SunOS 4.x
- PowerMac / Power MachTen 4.1.1 over MacOS
- Amiga 3000 running RedHat Linux 5.1 (Rawhide)

Patches to make it work on other platforms are welcome.


REQUIREMENTS:
=============

The following software is required to use Window Maker:

- X11R6.x
	Any version of X that has Shape Extension support will most likely
	work. We don't do anything fancy.

- autoconf, automake and libtool
	These tools are NOT needed, but IF you have one or
	more of them installed, make sure you have ALL of the following
	with exactly these versions:
		autoconf 2.59
		automake 1.9
		libtool 1.5

	If you have a different version, disable them by temporarily
	renaming them to something else or uninstalling them from your
	system. If you don't develop software you don't need them,
	so you can safely uninstall.

- libXPM 4.7 or newer
	Older versions may not work!!!
	Available at ftp://sunsite.unc.edu/pub/Linux/libs/X/


INSTALLATION:
=============

Build libDockApp (quick start guide)
------------------------------------
	For a quick start, type the following in your shell prompt:

	./configure
	make

	then, login as root and type:

	make install

	or if you want to strip the debugging symbols from the binaries and
	make them smaller, you can instead type:

	make install-strip

	This will build and install libDockApp with default parameters.

	(On some platforms you may need to run ldconfig with proper parameters.
	Check "man ldconfig" in those cases. On FreeBSD this is not necesarry
	as libtool already takes care of this for you during install phase)


Building a CVS version of libDockApp
------------------------------------
	If you use a version from CVS (which doesn't include some of the files
	generated by the GNU auto-tools), or in case the quick start method
	doesn't work for you, you can re-generate the build scripts from a clean
	build tree.

	If you have any Makefile's around, do a make distclean.
	Next, run the ./autogen.sh script in the base directory of libDockApp.

	If all goes well, you can continue with the quick start guide.

	If not, read the "Problems with GNU auto-tools" section.
	
If you're having problems with GNU auto-tools
---------------------------------------------
	The GNU auto-tools have a lot of trouble keeping different versions of
	the tools mutually compatible. Your problem is likely to be caused by
	that. If it's only your opinion causing the problems, you're right, but
	then this section isn't meant for you ;)

	You may be able to fix your problems by trying different versions of
	autoconf, automake/aclocal and libtool (change only one at a time!). If
	you didn't read the section "Building a CVS version of libDockApp", do
	that now. This section assumes you use the method described there.

	For your convenience environment variables LIBTOOLIZE, AUTOMAKE, ACLOCAL
	and AUTOCONF are available where you can specify the application to use.
	I use:
	    LIBTOOLIZE=libtoolize15
	    AUTOMAKE=automake19
	    ACLOCAL=aclocal19
	    AUTOCONF=autoconf259

	Another word of warning: You may be trying to use a version of aclocal
	that doesn't know about certain m4 files for specific libraries, if that
	version of aclocal (automake) was installed _after_ those libraries. You
	can usually fix this by copying (or linking) those files from other
	versions of aclocal (beware that you loose a link if you remove such
	"old" versions of aclocal that you, your sysadmin or your package
	maintainer deems them no longer necessary).

	Welcome to developer hell.

