SUBJECT: Compiling xemp

As I have only one system to test tcemp, don't expect it compile without
any troubles.

If you succeed, please let me know what you had to change to get it
working (please tell me also if there were no problems at all).
I'm also always willing to try to help you out with any problem you
might have (regarding xemp).

reply:	send to hjvissc@cs.vu.nl
or:	make reply
-------------------------------
STEP 1:   Creating the makefile

You will have to compile 'setup' to create a makefile for xemp.
The setup programm is located in the src directory:

command> cd src/setup
command> make

You'll be asked two questions:

1). Do you have getopt?
2). Do you have vsprintf?

Most of the systems do have these functions defined, but if setup doesn't
compile because one of those two is missing, enter:

command> make clean
command> make

And enter 'no' at the questions.

Now copies of my system are compiled, so probably it still
won't work. I can't help you now, you have to find those functions
yourself.

Otherwise, change to the xemp directory and run setup:

command> cd ../..
command> setup -vpt

Options to setup:
	-v:		Verbose, output what you're doing
	-p:		Do not depend on proto.h
	-i:		Check for existing makefile
	-t:		Do not ask questions about a X-environment.
			(tcemp only)
	-f <file>:	Generate <file> instead of makefile

Setup will ask you several questions. To take the default (answer between
square brackets], just type return. To enter nothing, type a dot (.)

Question 1:	Use which compiler
	Unless your c-compiler is located else, just accept the default
	value.

Question 2:	Are you working under BSD?
	Setup will try to check if you're working under BSD by trying
	to access "/usr/include/sys/termios.h". (access ok -> not bsd).
	Taking the default will work most of the time. (Unless your include
	directory is located elsewhere, then you'll have to check this
	yourself).

Question 3:	Flags to pass to the c-compiler
	Don't use O4 here, this generates even more core dumps (unless
	of course you have a better compiler as I do).

Question 4:	Flags to pass to the loader
	The options "-s" strips the executable (reduces its size)

The next page asks question about the empire game

Question 5:	World size
Question 6:	Default empire host
Question 7:	Default empire port
	These questions can be skipped if you don't know the answers right
	now. You can always set them: 1) In your environment, 2) In your
	.xemprc, and 3) On the command line.

Question 8:	Where will xemp-info be located?
	If setup can't access the directory, you'll be given a warning.
	
Question 9,10:	Do you have empire-info on line?
	If you have a local empire server, or just the info on line, 
	xemp doesn't need to get the info from the remote server, which
	will save you a lot of time.

Question 11:	Use as ctags
	Always ctags.

Question 12:	
	If you want to put xemp on ftp on your machine, you should 
	enter the directory where to put the tar-file.

After all these questions, setup will generate the makefile. If there
are any problems, you can send me mail, and I will take a look at it.
--------------------------------------------------------------------
STEP 2: Compiling

Now it's time to compile xemp. First we must create the correct 
proto.h file, so enter:

command> make tc_proto.h

proto.c (in src) will now be compiled, and proto.h will be made.

command> make tcemp

Get yourself a cup of coffee. This may take a while. If you have any
problems, I could try to help you out, but I'd prefer if you'd take a
look at the code yourself and send me a bug fix instead of a question.

If everything went ok, tcemp will be ready for use.

See: tcemp/startup tcemp/.xemprc tcemp/bindings
