File: README

package info (click to toggle)
craft 3.5-10
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 18,000 kB
  • ctags: 1,602
  • sloc: cpp: 3,794; makefile: 2,319; ansic: 857; sh: 385
file content (64 lines) | stat: -rw-r--r-- 1,876 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64

Source Code of CRAFT
====================

How to compile ?

You need the following things to compile craft :


- The file craftcc.tar.Z 
  (from ftp://borneo.gmd.de/pub/as/janus/craft/craftcc.tar.Z")

- The gnu g++, gcc command

- A shell-script interpreter

- The tar, compress command 

- and Xlib
 
Now you can start to do the following things.

- place craftcc.tar.Zin a new directory (e.g. craft) and "untar" it.

- edit "install" and change paths for libs and call of gnu stuff
  (only a few lines)

- execute install

If everything is proper it will take a bit to compile craft. If this
process is finished, you will have an executable craft in the
directory afterwards. Now you can call it.

Crafts needs a proper directory-structure which contains the various resource
files used by craft. Its structure looks like :

  craft         "the executable"
  .windefaults  "sugar for the window system"
  \buttons      "contains the button icons"
  \hcraft       "contains pictures of units and menus"

This structure is automatically produced during the unpacking of the source
code files. You should compile in the top directory of the above
directory tree.

Why no Makefile ?

I hate makefiles !!! This dammed stuff is always a good source for many
obsolete bugs. Therefore we don't use make for our projects, but
if you like to have a makefile, it should be easy to convert install.

Finally

The license of craft has been changed to the "Artistic License". See
http://set.gmd.de/~hua for details.

THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.

By the way if there are a few guys who are interested in further development
of the game, mail me. I would be interested to hear your ideas and tips.

E-mail: uwe.beyer@gmd.de