-
Notifications
You must be signed in to change notification settings - Fork 11
/
INSTALL.txt
145 lines (95 loc) · 4.18 KB
/
INSTALL.txt
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
COMPILING (Linux)
=================
Note: this section deals with compiling the Linux binary.
For information on compiling for Windows and macOS, see below.
Dependencies:
1. C++ compiler (GNU's G++) and associated tools
packages: g++ binutils
2. CMake
package: cmake
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. libXpm
package: libxpm-dev
5. OpenGL
(recommended but not strictly necessary, see below)
6. zlib
website: http://www.zlib.net/
package: zlib1g-dev
7. 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
commands will build the Eureka binary. (the '>' is just the prompt)
> mkdir build
> cd build
> cmake ..
> 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/
OpenGL is used to greatly speed up the 2D and 3D views, however
Eureka still supports software-only rendering as a compile-time
option. You will need to edit the Makefile and disable OpenGL
support -- look for the line containing NO_OPENGL and uncomment
that line, and remove all GL libraries from the build.
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 install
That will install the eureka binary, definition files for various
games and source ports, and the desktop and icon files.
COMPILING (macOS)
=================
Use CMake. You can download and install CMake from their website, or use a
third-party package manager such as Homebrew. Easiest to use is the graphical
interface version of CMake (CMake GUI).
Unlike on Linux, the CMake script will download and build FLTK from their
website. You don't need to download it yourself. This is by design, so that the
final built app is self-contained with all that it needs to run, and that it
will always use the exact same dependencies without varying on how the user may
have installed FLTK on their system.
The generated Xcode project or Makefile will ultimately produce an "Eureka Doom
Editor" graphical application. If you generated a Makefile, there's no "make
install" stage. Simply open the produced app.
DISTRIBUTING (macOS)
====================
To distribute a signed app of Eureka, you need to generate an Xcode project
first -- signing and notarizing the app is currently not supported from the
Makefile. You can also distribute the app generated by Makefile as-is, but users
will be warned that the app isn't signed, and prompted to move it to Trash
(unless they access the app from the right-click menu in Finder).
COMPILING (Windows)
===================
Use CMake, same as on macOS. Similarly, the FLTK project shall be downloaded and
built.
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 "~/.config/eureka/iwads" (or "$XDG_CONFIG_HOME/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.