File: INSTALL.txt

package info (click to toggle)
eureka 1.24-3
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 4,096 kB
  • sloc: cpp: 46,886; makefile: 133; objc: 114; sh: 85
file content (144 lines) | stat: -rw-r--r-- 3,701 bytes parent folder | download
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

COMPILING (Linux)
=================

Note: this section deals with compiling the Linux binary.
For information on compiling for Windows and MacOS X, see below.


Dependencies:

1. C++ compiler (GNU's G++) and associated tools
   packages: g++ binutils

2. GNU make
   package: make

3. FLTK 1.3
   website: http://www.fltk.org/
   package: libfltk1.3-dev

   You may also need: libxft-dev
                      libxinerama-dev
                      libfontconfig-dev
                      libjpeg-dev
                      libpng-dev

4. zlib
   website: http://www.zlib.net/
   package: zlib1g-dev

5. XDG Utils
   (only needed for Linux, to install the desktop and icon files)
   package: xdg-utils


Assuming all those dependencies are met, then the following shell
command will build the Eureka binary. (the '>' is just the prompt)

   > make


Some systems may need additional CFLAGS and/or LDFLAGS in order
to find the required libraries (especially FLTK).  For example,
the following is reported to work for Gentoo Linux:

   CFLAGS  += -I/usr/include/fltk-1
   LDFLAGS += -L/usr/lib64/fltk-1/



INSTALLING (Linux)
==================

First make sure the Eureka binary was compiled successfully.

Then become root (via the 'sudo' or 'su' command) and enter the
following shell command:

   > make full-install

That will install the eureka binary, definition files for various
games and source ports, and the desktop and icon files.

There is also a plain "install" target which does not run the
XDG utilities (which install the desktop and icon files).



COMPILING (Windows)
===================

The windows executable is built using a "cross compiler" under
Linux (or another OS supported by the MingW-w64 tools).

Sorry but compiling Eureka under Windows itself is not currently
supported.  If you want to do this, you will have to figure it
out on your own.


Dependencies:

1. C++ cross compiler and tools
   package: mingw-w64

2. GNU make
   package: make

3. FLTK 1.3.4
   website: http://www.fltk.org/

4. zlib
   website: http://www.zlib.net/


The FLTK and Zlib libraries must be in a directory called "lib_win32"
with the names "fltk-1.3.4" and "zlib-1.2.8" (these can be symlinks
to their actual location).  They both need to be cross-compiled with
MingW-w64.  For FLTK, these is some information on cross-compiling
in the "README.CMake.txt" document.

Assuming all those dependencies are met, then the following shell
command will build the Eureka binary. (the '>' is just the prompt)

   > make -f Makefile.xming



COMPILING (MacOS X)
===================

Compiling the MacOS X binary requires Xcode 4.

See the documents in the osx/ folder for more information.



SETTING UP Eureka
=================

Eureka requires an IWAD file from one of the supported games, for
example "doom2.wad".  Eureka will look for IWADs when it starts up,
but if it cannot find any then the 'Manage Wads' dialog will open
and you can browse for an IWAD file there, which will be remembered
for next time.

Places where Eureka looks for IWADs:

  1. The "iwads" directory in Eureka's home directory.  In Linux
     this will be "~/.eureka/iwads".  It is created automatically
     the first time Eureka is run (though there is no harm in
     creating it yourself).

  2. (a) In Linux: /usr/share/games/doom
     (b) In Windows: C:\DOOM and C:\DOOM2

  3. If you run Eureka from the command line and have the DOOMWADDIR
     or DOOMWADPATH environment variables set, then Eureka should find
     it the specified directory.

  4. If running from the command line, Eureka will look in the current
     directory for the IWAD.

  5. You can specify the IWAD file directly with the --iwad option.