Building EDuke32 on Linux
- 1 Compiling From Source
- 2 Installing EDuke32 globally
- 3 Notes
Compiling From Source
- You need an actual copy of Duke Nukem 3D. The shareware version can be found here
- Proper 3D acceleration drivers. NVIDIA has classically had the best Linux drivers.
- Proper MIDI install. The EDuke32 will appear to "randomly" crash without one. Use timidity for an easy software midi solution.
Getting source files
- Current version (You need to install the subversion program) :
svn co https://eduke32.svn.sourceforge.net/svnroot/eduke32/polymer/eduke32
- Source tarballs (Lite subversion snapshots, it does not include metadata, Apple compiled libraries, third-party jaudiolib and Photoshop files).
- Old and Older versions.
Prerequisites for the build
EDuke32 requires some development files installed before you can properly build.
- Basic dev environment (GCC >= 4.3.3, make, etc)
- Nasm (optional)
- LibGL and LibGLU (optional)
- LibSDL >= 1.2.10 or 1.3
- LibSDL Mixer > 1.2.6
- LibVorbis >= 1.1.2
- LibPNG >= 1.2.13 (optional)
- LibVPX >= 0.9.0 (optional)
- LibGTK+ >= 2.8.0 (optional)
On Debian / Ubuntu
sudo apt-get install build-essential nasm libgl1-mesa-dev libglu1-mesa-dev libsdl1.2-dev libsdl-mixer1.2-dev libvorbis-dev libpng12-dev libvpx-dev libgtk2.0-dev timidity freepats
On Fedora 14
sudo yum groupinstall "Development Tools"
sudo yum install SDL-devel SDL_mixer SDL_mixer-devel SDL_image-devel nasm libstdc++-devel libstdc++-static libpng-devel
Build the EDuke32
In a terminal window move to the EDuke32 sources folder and type
NOTE: with eduke32_src_20080924 and older GCC versions (< 4.3) remove;
-finline-small-functions -fpredictive-commoning options from
debug= options in
build/Makefile. Newer source releases do not have this problem.
If building fails with GCC version 4.4.X, try:
If it fails again, you can try with another version of GCC, for example:
It is possible to define some options during the build. Just add them before or after the 'make' command.
|PRETTY_OUTPUT||use colored output||1|
|USE_OPENGL||enable basic OpenGL Polymost renderer||1|
|POLYMER||enable fancy Polymer renderer||1|
|NOASM||disable the use of inline assembly pragmas||0|
|LINKED_GTK||enable compile-time linkage to GTK+||0|
|WITHOUT_GTK||do not compile GTK+ code||0|
|NEDMALLOC||use nedmalloc instead of malloc()||0|
|USE_LIBPNG||compile with libpng (used to make screenshots in the PNG format)||0|
|USE_LIBVPX||VP8 video codec used as an alternative to the ANM file format (only works if compiled with OpenGL support)||0|
|DEBUGANYWAY||include debug symbols even when generating release code||0|
|KRANDDEBUG||include logging of krand() calls for debugging the demo system||0|
|EFENCE||compile with Electric Fence for malloc() debugging||0|
|OPTLEVEL||GCC optimization strategy||2|
|LTO||enable link-time optimization, for GCC 4.5 and up||0|
Confirm successful compile
These files should now be present in the EDuke32 directory.
- mapster32 (executable)
- eduke32 (exectuable)
Use the game files
You need to have the original Duke Nukem files and the newly created EDuke32 executables in the same place. So, you could create a new folder (example eduke32_linux) and copy the original game files and the newly created EDuke32 executables there.
Run the game!
To run the game open up a terminal window, move to the proper directory and type :
- To use the High Resolution Pack you need to pass the -g parameter :
./eduke32 -g duke3d_hrp.zip hrp_update.zip maphacks.zip eduke32_mus.zip
- To use the Polymer HRP you need to pass the -g parameter :
./eduke32 -g polymer_hrp.zip polymer_upd.zip polymer_mhk.zip eduke32_mus.zip
- Using the autoload folder :
Copy mods or HRP files in the $HOME/.eduke32/autoload folder and it will be automaticaly loaded without additional parameters.
Installing EDuke32 globally
Installing EDuke32 as an application that you could run anywhere brings some useful advantages and is surprisingly easy to do.
EDuke32 will use the directory you are currently in as the directory to work in, as well as ~/.eduke32 (/home/yourname/.eduke32). This means that you could have a directory, copy a Duke Nukem TC (or mod) in there, cd to that directory and run the global EDuke32 binary without having to make even more copies of the same EDuke32 binaries. EDuke32 will adapt to use the GAME/USER.CON files it finds in the CURRENT directory.
All you'll have to do to get EDuke32 to run from anywhere is copy the eduke32 and mapster32 binaries to /usr/local/bin. After doing this, copy the duke3d.grp file to /usr/local/share/games/eduke32 or ~/.eduke32 (it's hidden, so try to cd to it or show hidden files). After this you'll be able to run EDuke32 from any directory on your hard disk!
Maps with extra resources Some maps that include extra resources might have trouble finding these new files (for example, an older version of Duke Plus won't be able to find Step#.wav and Grate#.wav sounds). The EDuke32 log will output a "file not found" error every time this happens. To fix this, change the names of these files to match the exact case given in EDuke32's log (for example, GRATE#.wav instead of Grate#.wav).
ART file inconsistency While most standard resources are referred to as UPPERCASE by EDuke32 (for example, GAME.CON), ART files are not as consistent and should be renamed to lowercase if you want to use custom art (tiles014.art instead of TILES014.ART).
Running with HRP Notes
If you want to run Polymer with the HRP you will need to provide the path to polymer_hrp.zip (even if its installed globally):
eduke32 -g /path/to/polymer_hrp.zip.
Running EDuke32 with an ATI card is slow for some users. One user has had success with a Radeon 4850 and Fedora 12 with the open source default driver plus the latest Mesa experimental - the game runs smooth and pretty fast.