Mercury MUD Driver SourceForge Logo
Home | News | Documentation | Building | Contributing | Release Plan

Mercury should build on any Unix-like platform (including Cygwin for Microsoft Windows.) If you have build problems with Mercury on any Unix-like platform, please submit a bug report with the platform, compiler, environment and build errors.

The makefiles and build scripts are currently set up to assume a GNU-esque build (autoconf configure script, makefiles, etc.) If you have an alternate build environment (such as one of the Windows IDEs), you'll have to look at the makefiles and set up the build yourself. There may also be some differences in platform library support that need to be taken into account in the source.

If you do manage to get it to build and function correctly, or have questions about how to do it let me know.

Starting with v0.0.6, I'm making a binary package for Windows users available that includes cygwin1.dll, which provides various POSIX functionality that the programs require. You do not have to download or install Cygwin to run this binary package. Note: you do have to have Cygwin installed in order to build from source.

Simply go to the Files link, download the mercury-win32-binary-0.0.6.zip file and unzip it. You can run the test programs from the directory that is created.

At this time, there are no other pre-built binaries for the Mercury MUD Driver. You have to build it yourself from source (but it's not as hard as you might think.)

If you're interested in installing Cygwin, which provides a Unix-like emulation layer for Windows, I recommend you use their web installer at the Cygwin homepage.

There are two ways you can obtain the Mercury MUD driver from source. First (and easiest) You can download the latest release from the project page. Simply click on the mercury-driver-0.0.1.tar.gz file for the latest release and follow the instructions to select a mirror. Be sure to check the release notes by clicking on the release name (e.g. CVS-20030818).

If you want to get the absolute bleeding edge, you can use anonymous CVS to get the latest source code. Naturally, this will be less stable than the release. You will also need the following tools (which are not required when building from the "official" release):

Note: anonymous CVS currently lags behind development by up to 24 hours, since SourceForge is running anonymous CVS from their backup servers. This should not be an issue for project developers.

The next step, after obtaining the source, is to prepare it for building. If you're building from the official release: If you're building from a CVS snapshot, you need to set up the build scripts first with automake and autoconf:

Once everything is set up, all you have to do is:

Mercury should not be installed at this point in time, so DO NOT make install. Run the driver and test programs from the source directory. See the release notes for more information.

Page maintained by Loiosh
Last modified October 06 2003 18:36:40.