… | |
… | |
13 | and using items and battle monsters. They can choose to cooperate |
13 | and using items and battle monsters. They can choose to cooperate |
14 | or compete in the same "world". |
14 | or compete in the same "world". |
15 | |
15 | |
16 | REQUIREMENTS |
16 | REQUIREMENTS |
17 | |
17 | |
18 | For UNIX, the ISO C++ 200x compiler are required to compile this game. In |
18 | For UNIX, a modern C++ compiler with some extensions is required to |
19 | addition, you will need the Perl development libraries along with the |
19 | compile this game. In addition, you will need the Perl development |
20 | following Perl modules: |
20 | libraries along with the following Perl modules (the server is tested |
|
|
21 | with perl 5.8.8 and 5.8-maint). |
21 | |
22 | |
22 | - Crossfire >= v0.97 |
23 | - Crossfire >= v0.97 |
23 | - Coro >= v3.5 |
24 | - Coro >= v3.5 |
24 | - Coro::Event >= v2.1 |
25 | - Coro::Event >= v2.1 |
25 | - Event >= v1.08 |
26 | - Event >= v1.08 |
… | |
… | |
31 | - Digest::MD5 >= v2.0 |
32 | - Digest::MD5 >= v2.0 |
32 | - Compress::LZF >= v1.71 |
33 | - Compress::LZF >= v1.71 |
33 | - Safe::Hole >= v0.10 |
34 | - Safe::Hole >= v0.10 |
34 | - Pod::POM >= v0.17 |
35 | - Pod::POM >= v0.17 |
35 | |
36 | |
36 | Furthermore, to build the crossfire server you will need the following: |
37 | Furthermore, you will need the following programs and libraries: |
37 | |
38 | |
38 | - gperf, the GNU perfect hash generator |
39 | - gperf, the GNU perfect hash generator >= v3.0 |
39 | - glib-2.0 >= v2.10 |
40 | - glib-2.0 >= v2.10 |
40 | - libpng >= v1.2 |
41 | - libpng >= v1.2 |
|
|
42 | - ImageMagick >= v6.0 |
|
|
43 | - optipng => v0.5.5 (http://optipng.sf.net) |
|
|
44 | - rsync >= 2.6 (a must have anyways) |
41 | |
45 | |
42 | Your compiler must support the Library Technical Report 1 extensions. |
46 | Your compiler must support the Library Technical Report 1 extensions and |
43 | The GNU C++ compiler >= version 4.0 does support these. |
47 | the upcoming typeof extension. The GNU C++ compiler >= version 4.0 does |
|
|
48 | support all these. |
44 | |
49 | |
45 | COMPILING |
50 | COMPILING |
46 | |
51 | |
47 | Crossfire has been known to compile on a wide variety of systems. It should |
52 | Crossfire has been known to compile on a wide variety of systems. It should |
48 | compile and most all ISO C++ 200x and POSIX compliant systems. |
53 | compile and most all ISO C++ 200x and POSIX compliant systems. |
49 | |
54 | |
50 | To get directions on compilation for UNIX/LINUX, read the INSTALL file. |
55 | To get directions on compilation for UNIX/LINUX, read the INSTALL file. |
51 | |
56 | |
52 | USAGE |
57 | USAGE |
53 | |
58 | |
54 | Crossfire runs on a client/server model. You will also need the client to |
59 | Crossfire runs on a client/server model. You will also need the client |
55 | play. You can either connect to a server someone else has set up, or run |
60 | to play. You can either connect to a server someone else has set up, |
56 | your own server and connect to that. The client package has information for |
61 | or run your own server and connect to that. The client package has |
57 | connecting to servers. |
62 | information for connecting to servers. |
58 | |
63 | |
59 | To run your own server, you need to make the crossfire binaries and install |
64 | To run your own server, you need to make the crossfire binaries |
60 | them, and then run the crossfire program. This now creates a server which |
65 | and install them, and then run the crossfire program. This now |
61 | you/other people can connect to. The map files will need to get downloaded |
66 | creates a server which you/other people can connect to. The map |
62 | and installed for the server to run properly. The maps should be unpacked in |
67 | files will need to get downloaded and installed for the server to run |
|
|
68 | properly. The map pack is released together with the server and can be |
|
|
69 | downloaded form the same location. The maps should be copied into the |
63 | the $(TARGET)/share/crossfire directory - after unpacking, you should have a |
70 | $(TARGET)/share/crossfire/maps directory - after unpacking, you should |
64 | $(TARGET)/share/crossfire/maps directory. |
71 | have a $(TARGET)/share/crossfire/maps/scorn directory. |
65 | |
72 | |
66 | If you plan to run a long term server, you should use one of the scripts |
73 | If you plan to run a long term server, you should use one of the scripts |
67 | provided that will re-run crossfire if it dies for some reason. |
74 | provided that will re-run crossfire if it dies for some reason. |
68 | |
75 | |
69 | WEB SITES: |
76 | WEB SITES: |