| … | |
… | |
| 16 | |
16 | |
| 17 | |
17 | |
| 18 | REQUIREMENTS |
18 | REQUIREMENTS |
| 19 | |
19 | |
| 20 | For UNIX, a modern C++ compiler with some extensions is required to |
20 | For UNIX, a modern C++ compiler with some extensions is required to |
| 21 | compile this game. In addition, you will need the Perl development |
21 | compile this game (g++ 4.x works). In addition, you will need the Perl |
| 22 | libraries along with the following Perl modules (the server is tested |
22 | development libraries along with the following Perl modules (the server |
| 23 | with perl 5.8.8 and 5.8-maint). |
23 | is tested with perl 5.8.8 and 5.8-maint) and their dependencies. (the |
|
|
24 | minimum versions below may not be up-to-date, the configure script will |
|
|
25 | check them all, though). |
| 24 | |
26 | |
|
|
27 | - AnyEvent >= 2.52 |
| 25 | - BDB >= v0.1 |
28 | - BDB >= v0.1 |
| 26 | - Compress::LZF >= v1.71 |
29 | - Compress::LZF >= v1.8 |
| 27 | - Coro >= v3.62 |
30 | - Coro >= v3.63 **SEE IMPORTANT NOTICE BELOW** |
| 28 | - Coro::Event >= v2.1 |
31 | - Coro::Event >= v2.1 |
| 29 | - Crossfire >= v0.97 |
32 | - Crossfire >= v0.98 |
| 30 | - Digest::MD5 >= v2.0 |
33 | - Digest::MD5 >= v2.0 |
| 31 | - Event >= v1.08 |
34 | - Event >= v1.08 |
| 32 | - IO::AIO >= 2.32 |
35 | - IO::AIO >= 2.32 |
| 33 | - JSON::XS => 1.11 |
36 | - JSON::XS => 1.21 |
| 34 | - Pod::POM >= v0.17 |
37 | - Pod::POM >= v0.17 |
| 35 | - Safe::Hole >= v0.10 |
38 | - Safe::Hole >= v0.10 |
| 36 | - Storable >= v2.0 |
39 | - Storable >= v2.0 |
| 37 | - Time::HiRes >= v1.0 |
40 | - Time::HiRes >= v1.0 |
| 38 | - YAML::Syck >= v0.71 |
41 | - YAML::Syck >= v0.71 |
| 39 | |
42 | |
|
|
43 | **NOTICE**: Crossfire uses an alternative signal stack, so you have to |
|
|
44 | use either the "u"context method or "a"ssembly when configuring Coro. |
|
|
45 | |
| 40 | Furthermore, you will need the following programs and libraries: |
46 | Furthermore, you will need the following programs and libraries: |
| 41 | |
47 | |
| 42 | - gperf, the GNU perfect hash generator >= v3.0 |
48 | - gperf, the GNU perfect hash generator >= v3.0 |
| 43 | - glib-2.0 >= v2.10 |
49 | - glib-2.0 >= v2.10 |
| 44 | - libpng >= v1.2 |
50 | - libpng >= v1.2 |
| 45 | - ImageMagick >= v6.0 |
51 | - ImageMagick >= v6.0 (possibly higher, depending on its bugs) |
| 46 | - optipng => v0.5.5 (http://optipng.sf.net) |
52 | - optipng => v0.5.5 (http://optipng.sf.net) |
| 47 | - pngnq >= 0.4 (http://freshmeat.net/redir/pngnq/53146/url_homepage/pngnq.html) |
53 | - pngnq >= 0.4 (http://freshmeat.net/redir/pngnq/53146/url_homepage/pngnq.html) |
| 48 | - rsync >= 2.6 (a must have anyways) |
54 | - rsync >= 2.6 (a must have anyways) |
| 49 | |
55 | |
| 50 | Your compiler must support the Library Technical Report 1 extensions and |
56 | Your compiler must support the Library Technical Report 1 extensions and |
| … | |
… | |
| 54 | On Debian GNU/Linux, you might get away with something like this for many of the |
60 | On Debian GNU/Linux, you might get away with something like this for many of the |
| 55 | above dependencies: |
61 | above dependencies: |
| 56 | |
62 | |
| 57 | apt-get install gperf optipng pngnq rsync imagemagick libglib2.0-dev libpng12-dev |
63 | apt-get install gperf optipng pngnq rsync imagemagick libglib2.0-dev libpng12-dev |
| 58 | apt-get install libpod-pom-perl libsafe-hole-perl libevent-perl |
64 | apt-get install libpod-pom-perl libsafe-hole-perl libevent-perl |
|
|
65 | |
|
|
66 | If you want to gte sensible backtraces for error conditions at runtime |
|
|
67 | to be logged you also need the external addr2line program (part of GNU |
|
|
68 | binutils) in your PATH. |
| 59 | |
69 | |
| 60 | |
70 | |
| 61 | COMPILING |
71 | COMPILING |
| 62 | |
72 | |
| 63 | Crossfire has been known to compile on a wide variety of systems. It should |
73 | Crossfire has been known to compile on a wide variety of systems. It should |
| … | |
… | |
| 71 | Crossfire runs on a client/server model. You will also a client to |
81 | Crossfire runs on a client/server model. You will also a client to |
| 72 | play. You can either connect to a server someone else has set up, or |
82 | play. You can either connect to a server someone else has set up, or |
| 73 | run your own server and connect to that. There are a number of clients |
83 | run your own server and connect to that. There are a number of clients |
| 74 | available, but the recommended one is CFPlus (see below for URL). |
84 | available, but the recommended one is CFPlus (see below for URL). |
| 75 | |
85 | |
| 76 | To run your own server, you need to make the crossfire binaries and |
86 | To run your own server, you need to build the crossfire server binaries |
| 77 | install them, and then run the crossfire program. This now creates a |
87 | and install them, then you will have to download and install map and |
| 78 | server which you/other people can connect to. First you have to download |
88 | archetype packs: |
| 79 | and install maps and archetype packs, though. |
|
|
| 80 | |
89 | |
| 81 | Download both the cfmaps-<version> and cfarch-<version> archives, then use cfutil |
90 | Download both the cfmaps-<version> and cfarch-<version> archives, then |
| 82 | to install both: |
91 | use cfutil to install both (the source directories must be writable for |
|
|
92 | this to work): |
| 83 | |
93 | |
| 84 | cfutil --install-maps path/to/cfmaps-<version>/ |
94 | cfutil --install-maps path/to/cfmaps-<version>/ |
| 85 | cfutil --install-arch path/to/cfarch-<version>/ |
95 | cfutil --install-arch path/to/cfarch-<version>/ |
| 86 | |
96 | |
| 87 | Both processes can take some time, depending on your resources :) |
97 | Both processes can take some time, depending on your resources :) If you |
|
|
98 | plan to repeat the installation you should specify the --cache option |
|
|
99 | which will keep costly-to-generate files around for further runs of |
|
|
100 | cfutil. |
|
|
101 | |
|
|
102 | Atfer this you can then run the crossfire executable. This starts a |
|
|
103 | server which you/other people can connect to. |
| 88 | |
104 | |
| 89 | |
105 | |
| 90 | WEB SITES: |
106 | WEB SITES: |
| 91 | |
107 | |
| 92 | The following web addresses have crossfire information that you may find |
108 | The following web addresses have crossfire information that you may find |
| … | |
… | |
| 104 | |
120 | |
| 105 | Bugs should be filed using the following email address: |
121 | Bugs should be filed using the following email address: |
| 106 | crossfire@schmorp.de |
122 | crossfire@schmorp.de |
| 107 | |
123 | |
| 108 | When reporting bugs, make sure you include the following: |
124 | When reporting bugs, make sure you include the following: |
|
|
125 | |
| 109 | o What version of crossfire did you use? |
126 | * What version of crossfire did you use? |
| 110 | o What type of computer did you use (CPU type) |
127 | * What type of computer did you use (CPU type) |
| 111 | o What is the version of the OS? |
128 | * What is the version of the OS? |
| 112 | o What windowing system are you using (e.g. openwindows, X.org, XFree86) |
129 | * What windowing system are you using (e.g. openwindows, X.org, XFree86) |
| 113 | o What compiler (and its version) did you use (e.g. gcc, acc)? |
130 | * What compiler (and its version) did you use (e.g. gcc, acc)? |
| 114 | o Which flags did you give it? |
131 | * Which flags did you give it? |
| 115 | o If the bug happens when compiling crossfire, send an EXACT copy of the |
132 | * If the bug happens when compiling crossfire, send an EXACT copy of the |
| 116 | compiler line, as well as the errors it puts out. Sending bugs of the |
133 | compiler line, as well as the errors it puts out. Sending bugs of the |
| 117 | sort 'it failed with a line like ...' doesn't help any. |
134 | sort 'it failed with a line like ...' doesn't help any. |
| 118 | o If the bug happened while running crossfire: |
135 | * If the bug happened while running crossfire: |
| 119 | - Include any output before to the bug. |
136 | - Include any output before to the bug. |
| 120 | - Give a description of what you did before the bug occured. The better |
137 | - Give a description of what you did before the bug occured. The better |
| 121 | detailed the description, the better chance I have of figuring |
138 | detailed the description, the better chance we have of figuring |
| 122 | out where the bug happened, or how I can recreate the bug. |
139 | out where the bug happened, or how we can recreate the bug. |
| 123 | - If possible, a stack trace from gdb (or other debugger) is very |
140 | - If possible, a stack trace from gdb (or other debugger) is very |
| 124 | helpful. |
141 | helpful. |
| 125 | |
142 | |
| 126 | The more information provided, the better chance of the bug being fixed in |
143 | The more information provided, the better chance of the bug being fixed |
| 127 | a timely fashion. |
144 | in a timely fashion. |
| 128 | |
145 | |
| 129 | SUBMITTING PATCHES: |
146 | SUBMITTING PATCHES: |
| 130 | |
147 | |
| 131 | Patches should be submitted to email address: |
148 | Patches should be submitted to email address: |
| 132 | crossfire@schmorp.de |
149 | crossfire@schmorp.de |
| 133 | |
150 | |
| 134 | PUBLIC SERVERS: |
151 | PUBLIC SERVERS: |
| 135 | |
152 | |
| 136 | The best way to find a server to play is to run the client |
153 | The best way to find a server to play is to run the client |
| 137 | and hit "Server List" in the setup dialog (this varies |
154 | and hit "Server List" in the setup dialog (this varies |
| 138 | depending on your client). You can also see a list at |
155 | depending on your client). You can also see a list at |
| 139 | http://crossfire.real-time.com/metaserver/. |
156 | http://crossfire.real-time.com/metaserver/. |
| 140 | |
157 | |
| 141 | The canonical server for use with Crossfire and CFPlus is |
158 | The canonical server for use with Crossfire and CFPlus is |
| 142 | crossfire.schmorp.de, port 13327 (default). |
159 | crossfire.schmorp.de, port 13327 (default). |
| 143 | |
160 | |
| 144 | COPYRIGHT |
161 | COPYRIGHT |
| 145 | |
162 | |
| 146 | Copyright (C) 2007 Crossfire Development Team |
163 | Copyright (C) 2006,2007 Crossfire TRT Development Team |
| 147 | Copyright (C) 2000, 2006 Mark Wedel |
164 | Copyright (C) 2000,2006 Mark Wedel |
| 148 | Copyright (C) 1992 Frank Tore Johansen |
165 | Copyright (C) 1992 Frank Tore Johansen |
| 149 | |
166 | |
| 150 | This program is free software; you can redistribute it and/or modify |
167 | This program is free software; you can redistribute it and/or modify |
| 151 | it under the terms of the GNU General Public License as published by |
168 | it under the terms of the GNU General Public License as published by |
| 152 | the Free Software Foundation; either version 2 of the License, or |
169 | the Free Software Foundation; either version 2 of the License, or |
| 153 | (at your option) any later version. |
170 | (at your option) any later version. |
| 154 | |
171 | |
| 155 | This program is distributed in the hope that it will be useful, |
172 | This program is distributed in the hope that it will be useful, |
| 156 | but WITHOUT ANY WARRANTY; without even the implied warranty of |
173 | but WITHOUT ANY WARRANTY; without even the implied warranty of |
| 157 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
174 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
| 158 | GNU General Public License for more details. |
175 | GNU General Public License for more details. |
| 159 | |
176 | |
| 160 | You should have received a copy of the GNU General Public License |
177 | You should have received a copy of the GNU General Public License |
| 161 | along with this program; if not, write to the Free Software |
178 | along with this program; if not, write to the Free Software |
| 162 | Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
179 | Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
| 163 | |
180 | |
| 164 | The authors can be reached via e-mail to crossfire@schmorp.de |
181 | The authors can be reached via e-mail to crossfire@schmorp.de |
