Building DreamZZT From Source

If there's no binary release for your system, or you just want the latest-and-greatest version of DreamZZT, you'll need to build DreamZZT from source.

Getting the source

Downloading a tarball

You can get the source for the latest released version of DreamZZT by clicking on the "Source" link in the Downloads section of the wiki.

Checking out from Subversion

If you want to stay up-to-date with the latest changes, or if you'd like to work on the source code, you'll need to check it out from Subversion. This guide will describe the process of using the command-line Subversion client, however Windows users may be interested in using a graphical front end like TortoiseSVN.

The first thing is to decide which version you want to check out. If you want the latest code, it's in a directory called "trunk". If you want a previous version, it's in a directory called tags.

To check out the latest development version:

svn co http://dev.c99.org/svn/DreamZZT/trunk DreamZZT

To check out a specific stable version (3.0.8 in this example):

svn co http://dev.c99.org/svn/DreamZZT/tags/RELEASE_3.0.8 DreamZZT

Building the Source

Getting Tiki

Tiki is the cross-platform library that DreamZZT uses to interface with different systems. Tiki is only available from Subversion, and can be checked out with the following command:

svn co https://svn.sourceforge.net/svnroot/cadcdev/tiki

Building Tiki

Windows

Open the Visual Studio project from the win32 folder. Modify the project search paths to include your OpenAL directory.

Mac OS X

Open the XCode project in the osx folder and click build.

Linux

cd sdl
make

Building DreamZZT

Windows

Open the Visual Studio project. Modify the project search paths to include your Tiki, OpenAL, and libcurl directories, and click build.

Mac OS X

Open the XCode project and click build.

Linux

Open the Makefile and make sure TIKI_DIR points to where the Tiki source is located.

Debian / Ubuntu:

debian/rules binary
dpkg-install ../dreamzzt_3.0.8_i386.deb

Other:

make
sudo make install

Commiting your changes

Creating a diff

If you've made modifications to the source code that you'd like to contribute, but you don't have write access to the source repository, you can create a diff file that you can attach to a ticket.

svn diff file1 file2 ... > my-great-patch.diff

Committing your changes

If you've been granted write access to the source repository, you can check in your changes with the following command:

svn commit file1 file2 ... -m "Description of my changes"