5 Note: this section deals with compiling the Linux binary.
6 For information on compiling for Windows and MacOS X, see below.
11 1. C++ compiler (GNU's G++) and associated tools
12 packages: g++ binutils
18 website: http://www.fltk.org/
19 package: libfltk1.3-dev
21 You may also need: libxft-dev
28 (recommended but not strictly necessary, see below)
31 website: http://www.zlib.net/
35 (only needed for Linux, to install the desktop and icon files)
39 Assuming all those dependencies are met, then the following shell
40 command will build the Eureka binary. (the '>' is just the prompt)
45 Some systems may need additional CFLAGS and/or LDFLAGS in order
46 to find the required libraries (especially FLTK). For example,
47 the following is reported to work for Gentoo Linux:
49 CFLAGS += -I/usr/include/fltk-1
50 LDFLAGS += -L/usr/lib64/fltk-1/
53 OpenGL is used to greatly speed up the 2D and 3D views, however
54 Eureka still supports software-only rendering as a compile-time
55 option. You will need to edit the Makefile and disable OpenGL
56 support -- look for the line containing NO_OPENGL and uncomment
57 that line, and remove all GL libraries from the build.
64 First make sure the Eureka binary was compiled successfully.
66 Then become root (via the 'sudo' or 'su' command) and enter the
67 following shell command:
71 That will install the eureka binary, definition files for various
72 games and source ports, and the desktop and icon files.
74 There is also a plain "install" target which does not run the
75 XDG utilities (which install the desktop and icon files).
82 The official windows executable is built using a "cross compiler"
83 under Linux, using the MingW-w64 tools.
85 Sorry but compiling Eureka under Windows itself is not currently
86 supported. If you want to do this, you will have to figure it
92 1. C++ cross compiler and tools
99 website: http://www.fltk.org/
102 The FLTK library must be in a directory called "lib_win32" with the
103 name "fltk-1.3.5" (it can be a symlink to the actual location), and
104 it needs to be cross-compiled with MingW-w64. Our makefile assumes
105 that FLTK was compiled to use its internal copies of the zlib, png
106 and jpeg libraries. FLTK has some information on cross-compiling
107 in the "README.CMake.txt" document.
109 Assuming all those dependencies are met, then the following shell
110 command will build the Eureka binary. (the '>' is just the prompt)
112 > make -f Makefile.xming
119 Compiling the MacOS X binary requires Xcode 4.
121 See the documents in the osx/ folder for more information.
128 Eureka requires an IWAD file from one of the supported games, for
129 example "doom2.wad". Eureka will look for IWADs when it starts up,
130 but if it cannot find any then the 'Manage Wads' dialog will open
131 and you can browse for an IWAD file there, which will be remembered
134 Places where Eureka looks for IWADs:
136 1. The "iwads" directory in Eureka's home directory. In Linux
137 this will be "~/.eureka/iwads". It is created automatically
138 the first time Eureka is run (though there is no harm in
139 creating it yourself).
141 2. (a) In Linux: /usr/share/games/doom
142 (b) In Windows: C:\DOOM and C:\DOOM2
144 3. If you run Eureka from the command line and have the DOOMWADDIR
145 or DOOMWADPATH environment variables set, then Eureka should find
146 it the specified directory.
148 4. If running from the command line, Eureka will look in the current
149 directory for the IWAD.
151 5. You can specify the IWAD file directly with the --iwad option.