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
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Obtaining and installing dopewars</title>
</head>
<body>
<h1>Obtaining and installing dopewars</h1>
<p>The dopewars source code and precompiled binaries (in RPM format) are
available from the main dopewars web page,
at <a href="http://dopewars.sourceforge.net/">
http://dopewars.sourceforge.net/</a>. Just follow the link from
there to the download section. "rpm" is the RedHat Package Manager, a program
for simplifying installation and upgrade of programs, and is part of the
RedHat Linux distribution. If you are using a different distribution, it
may be still be included, however. If you do not want to use "rpm", or the
installation fails, then you can obtain the source code tarball and recompile
the code from scratch.</p>
<p><b>Prerequisites:</b> dopewars relies on the GLib library for all builds;
this library is used for parsing the configuration files, network and string
handling, and many other purposes. On a Windows system, this is the only
prequisite; the standard Windows libraries are used for everything else. On a
Unix/Linux system, you will also need the screen library curses (or the
equivalent, such as ncurses or cur_colr) for the text-mode client, and the
<a href="http://www.gtk.org/">GTK+</a> libraries for the graphical client.</p>
<ul>
<li><a href="#win32">Windows installation</a></li>
<li><a href="#rpmbinary">RPM binary installation</a></li>
<li><a href="#rpmsource">RPM source installation</a></li>
<li><a href="#tarball">Tarball installation</a></li>
</ul>
<h2><a id="win32">Windows installation</a></h2>
<p>The easiest way to install the Windows version is to download the Windows
installer program from the
<a href="http://dopewars.sourceforge.net/download.html">download page</a>, and
run it (either instruct your web browser to "run from the current location",
or save it to somewhere obvious like the Desktop and then double-click on its
icon later). This should install all relevant files, and set up Start Menu
icons, etc. If, however, you wish to build the program from the source code,
see the <a href="#tarball">tarball installation</a> section below, and also
see the <a href="windows.html">Windows page</a>.</p>
<h2><a id="rpmbinary">RPM binary installation</a></h2>
<p>The binary RPMs are built for Intel (also Intel compatibles, such as AMD,
Cyrix, etc.) systems running RedHat Linux 9. On other systems, these binary
RPMs may refuse to install, or may run but then crash with mysterious
segmentation faults due to library conflicts.</p>
<ol>
<li>Download the
<a href="http://prdownloads.sourceforge.net/dopewars/dopewars-1.5.12-1.i386.rpm">
i386 (Intel)</a> RPM with your web browser. (If your browser is incorrectly set
up, it may try and display the file, in which case tell it explicitly to save
the file - Shift+Mouse button 1 in Netscape.)</li>
<li>Become root on your Unix box (if you cannot become root, then you will
probably not be able to use RPM installation, depending on how "rpm" is set
up).</li>
<li>Change to the directory containing the dopewars rpm, and install it with
the command<br />
<tt><b>rpm -Uvh dopewars-1.5.12-1.i386.rpm</b></tt><br /> This will replace any
already-installed earlier version.</li>
</ol>
<h2><a id="rpmsource">RPM source installation</a></h2>
<p>This route is open to you if your system has "rpm", but the binary RPMs do
not work on your system, or your machine is not an Intel (an Alpha or PowerMac,
for example). It involves obtaining the RPM of the source code, and then
building the binaries from it on your system.</p>
<ol>
<li>Download the
<a href="http://prdownloads.sourceforge.net/dopewars/dopewars-1.5.12-1.src.rpm">
source code RPM</a>.</li>
<li>Become root and change to the directory containing the new rpm.</li>
<li>Build a binary rpm with the command<br />
<tt><b>rpm --rebuild dopewars-1.5.12-1.src.rpm</b></tt></li>
<li>Change to the directory which the binary rpm has been written to (check
the output of the above - usually /usr/src/redhat/RPMS/<i>xxx</i>, where
<i>xxx</i> is your machine type - for example, "i386" on Intel machines,
"alpha" on Alphas, "x86_64" on AMD64 or EM64T machines)</li>
<li>Install the binary rpm with the command<br />
<tt><b>rpm -Uvh dopewars-1.5.12-1.<i>xxx</i>.rpm</b></tt></li>
</ol>
<h2><a id="tarball">Tarball installation</a></h2>
<p>If you don't have, or don't want to use, RPM, you can obtain the source code
in gzipped, tarred ("tarball") format and recompile and install it yourself.
This is also usually a necessity if you cannot become root (the superuser) on
your Unix box, or if you wish to build the Windows version from source code.</p>
<p>Before beginning, you should ensure that you have all the necessary
prequisites (see above). To compile on a Windows system, you should install
the free <a href="http://sourceware.cygnus.com/cygwin/">Cygwin</a> suite, and
use the included compiler. (You could use a different C/C++ Windows compiler,
but you'll have to write your project files if you do this.) On either Windows
or Unix systems, you will need to get the GLib library first, available for
Unix <a href="http://www.gtk.org/download/">here</a> or for Windows
<a href="http://www.gimp.org/win32/downloads.html">here</a>.</p>
<ol>
<li>Download the
<a href="http://prdownloads.sourceforge.net/dopewars/dopewars-1.5.12.tar.gz">
source code tarball</a>.</li>
<li>Change to the directory containing the tarball and extract the contents
with the command <br />
<tt><b>tar -xvzf dopewars-1.5.12.tar.gz</b></tt><br />
(or similar).</li>
<li>Change into the dopewars-1.5.12 directory, and read all the important
documentation in there ;) Most notably, the INSTALL file gives more details
on setup and installation on Windows systems.</li>
<li>Build the binary with the commands<br />
<tt><b>./configure</b><br />
<b>make</b></tt></li>
<li>Become root and install the dopewars files with<br />
<tt><b>make install</b></tt><br />
<p>The configure script will test your system and set up dopewars so that it
should compile cleanly. If you are running the Cygwin tools under Microsoft
Windows, the script should detect this and allow you to build a native
Windows binary; this will then run on any Win32 system, even one without Cygwin
installed. The configure script supports a number of configurable options; for
more details, read the INSTALL file in the dopewars-1.5.12 directory.</p>
<p>If you cannot become root, run the configure script specifying directories
for which you have write access for the dopewars files, with a command
such as<br />
<tt><b>./configure --prefix=/home/user/dopewars</b></tt></p></li>
</ol>
<hr />
<ul>
<li><a href="index.html">Main index</a></li>
</ul>
<p>
Last update: <b>28-07-2003</b><br />
Valid <a href="http://validator.w3.org/check/referer">XHTML 1.1</a>
</p>
</body>
</html>
|
