Difference between revisions of "User:HunterZ"

From DOSBoxWiki
Jump to: navigation, search
Line 1: Line 1:
 
'''
 
'''
=CVS Builds=
+
=SVN Builds=
This article is a discussion of the general purpose of DOSBox CVS builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various DOSBox CVS-related questions; it is followed by a listing, description of and links to known CVS builds, as well as a selection of useful related links.  
+
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 DOSBox SVN-related questions; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.  
  
==What are CVS builds?==
 
CVS builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called a CVS repository. CVS builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced CVS builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.
 
  
==Why should I get a CVS build?==
+
==What are SVN builds?==
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 CVS 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 a CVS 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.
+
SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called a 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 get a 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 a 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?==
 
==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 a CVS 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) CVS build. Also, see replies to this post from the maintainers for additional info on their builds.
+
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 a 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?==
 
==How do I use it?==
First, install the latest official release of DOSBox. Then, unpack the CVS build over the top of it, replacing the release versions of the files with the CVS 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 [http://vogons.zetafleet.com/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.
+
First, install the latest official release of DOSBox. 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 [http://vogons.zetafleet.com/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.
 +
 
 +
 
 +
==What do I do if I find bugs in a 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 [http://vogons.zetafleet.com/viewtopic.php?t=2949 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?==
 +
Please feel free to discuss SVN build-related topics in the [http://vogons.zetafleet.com/viewtopic.php?t=9306 forum thread] where this article originally started.
  
==What do I do if I find bugs in a CVS 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 [http://vogons.zetafleet.com/viewtopic.php?t=2949 help request guidelines]). ''Update:'' Note that bugs in plain CVS 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 CVS source code.
 
  
==Where can I go to talk about CVS builds?==
+
==List of SVN builds==
Please feel free to discuss CVS build-related topics in the [http://vogons.zetafleet.com/viewtopic.php?t=9306 forum thread] where this article originally started.
+
  
==List of CVS builds==
 
  
===Plain vanilla CVS builds===
+
===Plain vanilla SVN builds===
The following CVS builds are based directly off of the official DOSBox CVS source code. Use these builds to test the latest official CVS changes.
+
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.
  
 
====EmuCR====
 
====EmuCR====
Line 36: Line 44:
 
* Notes: '''Daily builds seem to have stopped as of 3/28/10.'''
 
* Notes: '''Daily builds seem to have stopped as of 3/28/10.'''
  
===Enhanced CVS builds===
+
 
The following CVS 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 CVS. 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.
+
===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.
  
 
====ykhwong====
 
====ykhwong====
Line 53: Line 62:
 
* URL: http://www.si-gamer.net/gulikoza/
 
* URL: http://www.si-gamer.net/gulikoza/
 
* Notes: Build of DOSBox focused on GLIDE support.
 
* Notes: Build of DOSBox focused on GLIDE support.
 +
  
 
===Unofficial ports===
 
===Unofficial ports===
Line 93: Line 103:
 
* URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742
 
* URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742
  
===Obsolete CVS builds===
+
 
 +
===Obsolete SVN/CVS builds===
 
These builds are no longer maintained and are listed here for historical reference.
 
These builds are no longer maintained and are listed here for historical reference.
  
Line 110: Line 121:
 
* Last updated: October 15, 2004
 
* Last updated: October 15, 2004
 
* URL: http://www.artworxinn.com/alex/downloads.htm
 
* URL: http://www.artworxinn.com/alex/downloads.htm
* 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 CVS builds.
+
* 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.
  
 
====pDOSBox for Pocket PC====
 
====pDOSBox for Pocket PC====
 
* URL: http://www.e-lation.net/site/emufor_Pocket_PC.html
 
* URL: http://www.e-lation.net/site/emufor_Pocket_PC.html
 +
  
 
==Other useful links==
 
==Other useful links==
  
===Snapshot of latest DOSBox CVS source code===
+
 
 +
===Snapshot of latest DOSBox SVN source code===
 
* URL: http://dosbox.linuxsecured.net/dosboxcvs.tgz
 
* URL: http://dosbox.linuxsecured.net/dosboxcvs.tgz
  
===CVS Changelog===
+
===SVN Changelog===
 
* URL: http://dosbox.linuxsecured.net/dosboxcvs.txt
 
* URL: http://dosbox.linuxsecured.net/dosboxcvs.txt
 
* URL: http://cvscompile.aep-emu.de/cl/dosboxChangeLog.txt
 
* URL: http://cvscompile.aep-emu.de/cl/dosboxChangeLog.txt
 
* Description: List of latest changes in the DOSBox SVN source code repository.
 
* Description: List of latest changes in the DOSBox SVN source code repository.
  
===CVS section of DOSBox Wiki===
+
===DOSBox Wiki article on making your own SVN build from the DOSBox source code===
 
* URL: [[BuildingDOSBox]]
 
* URL: [[BuildingDOSBox]]
  
Line 140: Line 153:
 
* URL: http://sourceforge.net/projects/dosbox
 
* URL: http://sourceforge.net/projects/dosbox
  
===DOSBox CVS build news===
+
===DOSBox SVN build news===
 
* URL: http://www.emucr.com/search/label/DOSBox
 
* URL: http://www.emucr.com/search/label/DOSBox
* Description: EmuCR posts with DOSBox tag (DOSBox CVS builds, news regarding frontends and other DOSBox ports)
+
* Description: EmuCR posts with DOSBox tag (DOSBox SVN builds, news regarding frontends and other DOSBox ports)

Revision as of 21:40, 25 October 2010

SVN Builds

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 DOSBox SVN-related questions; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.


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 sourceforge.net in something called a 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 get a 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 a 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 a 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?

First, install the latest official release of DOSBox. 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 a 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?

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


List of SVN builds

Plain vanilla 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.

EmuCR

Tharos


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.

ykhwong

  • Last updated: April 11, 2010
  • URL: http://ykhwong.x-y.net/page.htm
  • Notes: The Windows build incorporates vasyl's experimental emulation of various SVGA chipsets, OpenGL-HQ, Direct3D, Glide emulation, munt mt32 emulation, Improved IPX support, Virtual Printer support, PhysFS support (Mount .zip files), Overscan Border patch.

DOSBox "Mega Build" series (by HAL 9000)

gulikoza


Unofficial ports

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

DOSBox 0.72 for AmigaOS 4.0

DOSBox for OS/2

DOSBox v0.60 for Dreamcast

DOSBox for GP2x

DOSBox for IRIX

DOSBox for PSP

DOSBox for Pocket PC (by n0p)

DOSBox 0.70 Optimized for PXA270 (iwmmxt)


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: http://garni.ch/dosbox/
  • 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.
  • Note: 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 for Mac OSX (by rhoenie/Marcus Herbert)

DOSBox with MT-32 emulation (by Canadacow)

  • Last updated: October 15, 2004
  • URL: http://www.artworxinn.com/alex/downloads.htm
  • 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.

pDOSBox for Pocket PC


Other useful links

Snapshot of latest DOSBox SVN source code

SVN Changelog

DOSBox Wiki article on making your own SVN build from the DOSBox source code

DOSBox compatibility Database

DOSBox Debug Build

DOSBox home page

DOSBox sourceforge project page

DOSBox SVN build news