In order to build Nikwi you will need:

	1. bmake - get it from http://www.slashstone.com/more/bmake
	2. libbadcfg - get it from http://www.slashstone.com/more/badcfg
	3. libslashfx - this is included with Slashstone SoundFX Builder. Get it
		from http://www.slashstone.com/.
	4. SDL - get it from http://www.libsdl.org/
	
	For Win32 builds, you'll also need MinGW and MSYS. Get both of them from
	http://www.mingw.org/. You'll need to update your PATH environment
	variable to include MinGW binaries in order to use the included GCC
	compiler.

	MSVC, Borland C/C++ and other compilers are *NOT* supported.
	
Note: place the library directories (except SDL) to this directory. The
makefiles expect to find them here.

Once you have the tools, you will need to build the libraries. Most libraries
require bmake to be in the PATH environment variable (you can also type the full
path to the executable, but i don't recommend using bmake that way).

Note that before using bmake you need to build it first (the site above doesn't
contain binaries). So before you build the required libraries, you need to build
bmake.

When you have bmake ready, build the libraries in the following order:

	1. libbadcfg
	2. slashfx
	3. slashtdp (included in the archive)
		Note: under Win32 the build of the demo may fail. Ignore the
		error message, the library should be ok.
	4. us (UndeadScript - included in the archive)

Then you can build the game itself.

Note that the data/ subdirectory does *NOT* contain the converted image files
(*.ut files). These must be created from the images in the images/ subdirectory
using the bmp2ut tool (included in the tools/ subdirectory) and the makedata.sh
BASH script (note: this has only been tested under Linux - it may not work under
Win32/MSYS). If you don't plan to modify the images, just use the data file
found in the binary distribution.

When you make the data files, they will be inside the data/ subdirectory. If you
want to distribute the game, you can distribute the data/ subdirectory itself or
you can create the "justdata.up" archive using the upack tool found in the
tools/ subdirectory. If you use ZIP files for your distribution it is
recommended to distribute a justdata.up file instead of the data/ directory
because the compression will be more efficient.

