Building Chocolate Doom on BSD

From Chocolate Doom

Building Chocolate Doom on *BSD can be slightly more involved than on Linux, however it is not difficult.

Table of contents
1 OpenBSD

1.1 Requirements
1.2 Fetching the source code via SVN
1.3 Compiling the source code from official release
1.4 Compiling the source code from SVN
1.5 TiMidity

[edit]

OpenBSD

[edit]

Requirements

In order to compile Chocolate Doom, you will need the following (see [1] (http://www.openbsd.org/faq/faq15.html#PkgMgmt) for installing packages on OpenBSD):

  • X.Org/Xenocara, if you do not have it please see [2] (http://www.openbsd.org/faq/faq4.html#AddFileSet) and install the x*.tgz file sets.
  • Base compiling environment (gcc must be installed), if you do not have it see [3] (http://www.openbsd.org/faq/faq4.html#AddFileSet) and install the comp??.tgz file set.
  • autoconf - There are multiple versions available, this guide was specifically tested with autoconf-2.61p1.
  • automake - There are multiple versions available, this guide was specifically tested with automake-1.9.6p1.
  • SDL - you must have installed at least sdl (theres two flavors, -esd and -sun, I don't think it'd make a difference but for reference, I have -sun installed), sdl-mixer, sdl-net, and sdl-sound.
  • Subversion - only if you need to compile the latest and greatest source code.
[edit]

Fetching the source code via SVN 

svn co https://chocolate-doom.svn.sourceforge.net/svnroot/chocolate-doom/trunk/chocolate-doom
[edit]

Compiling the source code from official release 

cd chocolate-doom-1.0.0
./configure
make
sudo make install

Enjoy!

[edit]

Compiling the source code from SVN

Unlike most Linux systems, OpenBSD does not have AUTOMAKE_VERSION or AUTOCONF_VERSION automatically set (as it does not include autoconf or automake in the base system anyhow). These will need to be set first. 

export AUTOMAKE_VERSION=1.9 # Change to your native automake version
export AUTOCONF_VERSION=2.61 # Change to your native autoconf version
./autogen.sh --mandir=/usr/local/man
  # If you would like to install to any directory than /usr/local, add --prefix=/directory; change the mandir too
  # By default OpenBSD does not check /usr/local/share/man, which is where it would normally install the manpage
make
sudo make install # Or use su, or run as root, or just `make install` if you're installing to $HOME

Also unlike most Linux systems, neither /usr/games nor /usr/local/games is set by the shell by default in OpenBSD. You can either add those paths to your $PATH automatically ($HOME/.kshrc, $HOME/.bash_profile, etc), or copy the binaries to /usr/bin or /usr/local/bin (your preference).

Ideally, you should copy your IWADs to /usr/local/share/games/doom, as that would be the (default) directory Chocolate Doom will look for the files.

[edit]

TiMidity

If running OpenBSD 4.2 or higher, install TiMidity to play background music. Older versions of OpenBSD contain a broken sdl-mixer package which will crash Doom ports (see [4] (http://bugzilla.libsdl.org/show_bug.cgi?id=118)); if you must have TiMidity installed on an older release, you can just disable the background music via chocolate-setup to enjoy a crash-free experience.

Retrieved from "http://www.chocolate-doom.org/wiki/index.php/Building_Chocolate_Doom_on_BSD"