SVN Builds

From DOSBoxWiki
Revision as of 22:56, 25 October 2010 by HunterZ (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This article is a discussion of the general purpose of DOSBox SVN builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various questions regarding DOSBox SVN builds; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.

SVN Builds FAQ

What are SVN builds?

SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on in something called an SVN repository. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.

Why should I use an SVN build?

Every so often a new official version of DOSBox is released. However, active development continues between releases, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. You may also want access to the new features or optimizations if you are having compatibility or performance issues.

Which one should I use?

That's up to you. Consult the list below to see which features the different builds contain and decide which one you want to try first. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Also, see replies to this post from the maintainers for additional info on their builds.

How do I use it?

Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Other builds contain only a custom dosbox executable binary (e.g. dosbox.exe) and possibly some supporting libraries, and require that you first install the latest official release of DOSBox and then unpack the SVN build over the top of it - replacing the release versions of the files with the SVN versions. Some developers also recommend regenerating your dosbox.conf configuration file so that you will see any new config options that have been added. Consult this forum thread for info on how to regenerate a config file.

What do I do if I find bugs in an SVN build?

First, search the DOSBox community forums to see if it's already been reported. If it hasn't, post as much information as possible (see the help request guidelines). Update: Note that bugs in plain SVN builds are probably the only ones of interest to the DOSBox developers. Problem reports for the other builds should be addressed to their respective maintainers, as problems could be caused by experimental patches that aren't part of the official SVN source code.

Where can I go to talk about SVN builds? (forum thread)

Please feel free to discuss SVN build-related topics in the forum thread where this article originally started.

List of SVN Builds

Plain/vanilla/clean SVN builds

The following SVN builds are based directly off of the official DOSBox SVN source code. Use these builds to test the latest official SVN changes.

Enhanced SVN builds

The following SVN builds contain additional fixes and/or features that are not officially part of DOSBox. Many people prefer them due to the included extra features that are not included in in the SVN. Note that if you have problems with these builds, it may be due to the unofficial changes that have been made by their maintainers and not the official DOSBox code itself that is to blame.

  • DOSBox "Mega Build" series by HAL 9000

Unofficial ports

These builds are for other Operating Systems and are not in any way supported by the DOSBox team.

Obsolete SVN/CVS builds

These builds are no longer maintained and are listed here for historical reference.

  • DOSBox CVS for Linux (by Moe)
    • Last updated: December 15, 2006
    • URL:
    • Description: Recently Moe has decided to provide a DOSBox Linux (x86, 32-bit, Athlon64-optimized) binary including some useful patches. It is built against latest CVS and includes at least these patches: addkey, adlib optimize, Innovation SSI-2001, Self-Modifying-Code optimizations, SVGA chipsets, CD-Image cycling, Glide emulation, Printer emulation.
    • Notes: Moe is also the creator of OPENGL-HQ. OPENGL-HQ is another scaler that is implemented in SDL.dll. Unfortunately it may be some time (or never), until OPENGL-HQ is implemented in the official SDL so until then you'll have to download it from here (or compile it yourself). Neat thing about this is that you can use this SDL.DLL with any SDL program (e.g. DOSBox, SCUMMVM...).

  • DOSBox with MT-32 emulation (by Canadacow)
    • Last updated: October 15, 2004
    • URL:
    • Description: This build is no longer useful; it was made before DOSBox 0.63 came out and contains MT-32 emulation code that is much older than the current Munt releases. Note that more current MT-32 emulation is also included as an unofficial feature of some of the newer SVN builds.

Useful Links

SVN changelog

The following links list the latest changes to the official DOSBox source code on its SVN repository:

SVN build news

The following link(s) provide news related to DOSBox SVN builds:

Debugger-enabled builds

Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:

Making your own SVN build

The following DOSBoxWiki article discusses the process of making your own SVN build from the official DOSBox SVN source code:

Snapshot of latest DOSBox SVN source code

Snapshots of the latest SVN versions of the DOSBox source code are available at the following URL(s) :