1 |
root |
1.1 |
How to Install a Crossfire Server on Windows: |
2 |
|
|
|
3 |
|
|
Please follow the steps in the right order! |
4 |
|
|
|
5 |
|
|
o First step: Before you can compile the Crossfire source, |
6 |
|
|
you must install a python script engine on your computer. |
7 |
|
|
Python is the default script engine of Crossfire. |
8 |
|
|
You can find the python engine here: http://www.python.org/. |
9 |
|
|
The current Crossfire server use Python 2.1.1 . |
10 |
|
|
The Package comes with Installer and pre compiled libs & dlls, |
11 |
|
|
you have only to install them. The VisualC Crossfire settings are for |
12 |
|
|
d:\python21 . You can install the package of course on a different |
13 |
|
|
spot, but you habe then to change the pathes in the VC settings. |
14 |
|
|
Go in Settings/C++ and Settings/Link and change the optional |
15 |
|
|
include and libs path to the new python installation path. |
16 |
|
|
|
17 |
|
|
o 2nd step: Go in make_win32 (this is the same folder where this |
18 |
|
|
doc should be) and run "installwin32.bat"! Be sure you do this before |
19 |
|
|
you compile! The bat-file will make & copy all folders and files |
20 |
|
|
you need to run the server later, except the maps! |
21 |
|
|
You must download a map package and install them the share folder. |
22 |
|
|
Its must look like this: crossfire\share\maps\... . |
23 |
|
|
|
24 |
|
|
o 3rd step: You must compile the program. You'll need |
25 |
|
|
Visual C++ to do this (or some other ANSI C-compiler that can |
26 |
|
|
read *.dsw files). After unpacking the crossfire package, doubleclick |
27 |
|
|
on "crossfire32.dsw". |
28 |
|
|
There are 3 projects in your Workspace: Crossfire32 (the server), |
29 |
|
|
libcross.lib and plugin_python . You need to compile all 3. Easiest |
30 |
|
|
way is to select the plugin_python - ReleaseLog as active Project, |
31 |
|
|
this will compile all others too. |
32 |
|
|
Then - in Visual C++ - press <F7> to compile. |
33 |
|
|
If you don't have an appropriate compiler you can try to get |
34 |
|
|
the binary (crossfire32.exe file and plugin_python.dll) from *somewhere*. |
35 |
|
|
After the compiler is successul, the VC copies the crossfire32.exe in the |
36 |
|
|
"crossfire" folder and the plugin_python.dll in the crossfire/share/plugins |
37 |
|
|
folder. |
38 |
|
|
|
39 |
|
|
NOTE: The compiling will give you >400 warning messages. Thats |
40 |
|
|
some casting warnings from the original unix source - they are |
41 |
|
|
not harmfull. Ignore them, we will remove it when we get |
42 |
|
|
time for it. |
43 |
|
|
|
44 |
|
|
o Last step: Run the program "crossfire32.exe" (in the directory |
45 |
|
|
"crossfire"). A dos-prompt should open now, showing lots of |
46 |
|
|
weird text: the server logs. |
47 |
|
|
You're done - the server is up and ready for connections. :-) |
48 |
|
|
|
49 |
|
|
If you still have troubles, write to the Crossfire mailing list: |
50 |
|
|
<crossfire-list@lists.real-time.com>. Doing so, please |
51 |
|
|
provide as much information on your problem as possible! |
52 |
|
|
Most important: Tell us exactly what version of crossfire |
53 |
|
|
you've used. If it's an old version, update first and see if |
54 |
|
|
that solves your problem. |