| ---
tinstallation.html (6378B)
---
1
2
3
5
6
7
8
9 Obtaining and installing dopewars
10
11
12
13
14 Obtaining and installing dopewars
15
16 The dopewars source code and precompiled binaries (in RPM format) are
17 available from the main dopewars web page,
18 at
19 https://dopewars.sourceforge.io/. Just follow the link from
20 there to the download section. "rpm" is the RedHat Package Manager, a program
21 for simplifying installation and upgrade of programs, and is part of the
22 RedHat Linux distribution. If you are using a different distribution, it
23 may be still be included, however. If you do not want to use "rpm", or the
24 installation fails, then you can obtain the source code tarball and recompile
25 the code from scratch.
26
27 Prerequisites: dopewars relies on the GLib library for all builds;
28 this library is used for parsing the configuration files, network and string
29 handling, and many other purposes. On a Windows system, this is the only
30 prequisite; the standard Windows libraries are used for everything else. On a
31 Unix/Linux system, you will also need the screen library curses (or the
32 equivalent, such as ncurses or cur_colr) for the text-mode client, and the
33 GTK+ libraries for the graphical client.
34
35
41
42
43 The easiest way to install the Windows version is to download the Windows
44 installer program from the
45 download page, and
46 run it (either instruct your web browser to "run from the current location",
47 or save it to somewhere obvious like the Desktop and then double-click on its
48 icon later). This should install all relevant files, and set up Start Menu
49 icons, etc. If, however, you wish to build the program from the source code,
50 see the tarball installation section below, and also
51 see the Windows page.
52
53
54 The binary RPMs are built for Intel systems running RedHat or Fedora Linux.
55 On other systems, these binary RPMs may refuse to install, or may run but then
56 crash with mysterious segmentation faults due to library conflicts.
57
58
59 - Download the
60
61 x86_64 (64-bit Intel for RedHat Enterprise 7) RPM with your web browser.
62
63 - Become root on your Unix box (if you cannot become root, then you will
64 probably not be able to use RPM installation, depending on how "rpm" is set
65 up).
66
67 - Change to the directory containing the dopewars rpm, and install it with
68 the command
69 rpm -Uvh dopewars-1.6.1-1.el7.x86_64.rpm
This will replace any
70 already-installed earlier version.
71
72
73
74 This route is open to you if your system has "rpm", but the binary RPMs do
75 not work on your system, or your machine is not an Intel (an Alpha or PowerMac,
76 for example). It involves obtaining the RPM of the source code, and then
77 building the binaries from it on your system.
78
79
80 - Download the
81
82 source code RPM.
83
84 - Become root and change to the directory containing the new rpm.
85
86 - Build a binary rpm with the command
87 rpmbuild --rebuild dopewars-1.6.1-1.el7.src.rpm
88
89 - Change to the directory which the binary rpm has been written to (check
90 the output of the above - usually /usr/src/redhat/RPMS/xxx, where
91 xxx is your machine type - for example, "i386" on Intel machines,
92 "alpha" on Alphas, "x86_64" on AMD64 or EM64T machines)
93
94 - Install the binary rpm with the command
95 rpm -Uvh dopewars-1.6.1-1.el7.xxx.rpm
96
97
98
99 If you don't have, or don't want to use, RPM, you can obtain the source code
100 in gzipped, tarred ("tarball") format and recompile and install it yourself.
101 This is also usually a necessity if you cannot become root (the superuser) on
102 your Unix box, or if you wish to build the Windows version from source code.
103
104 Before beginning, you should ensure that you have all the necessary
105 prequisites (see above). To compile on a Windows system, you will need
106 the MinGW compiler and libraries; see the
107 Windows-specific
108 build page for more information.
109
110
111
112 - Download the
113
114 source code tarball.
115
116 - Change to the directory containing the tarball and extract the contents
117 with the command
118 tar -xvzf dopewars-1.6.1.tar.gz
119 (or similar).
120
121 - Change into the dopewars-1.6.1 directory, and read all the important
122 documentation in there ;) Most notably, the INSTALL file gives more details
123 on setup and installation.
124
125 - Build the binary with the commands
126 ./configure
127 make
128
129 - Become root and install the dopewars files with
130 make install
131 The configure script will test your system and set up dopewars so that it
132 should compile cleanly. The configure script supports a number of
133 configurable options; for more details, read the INSTALL file in the
134 dopewars-1.6.1 directory.
135
136 If you cannot become root, run the configure script specifying directories
137 for which you have write access for the dopewars files, with a command
138 such as
139 ./configure --prefix=/home/user/dopewars
140
141
142
143
146
147 Last update: 06-12-2020
148 Valid XHTML 1.1
149
150
151 |