DOSBoxWiki - User contributions [en]

Building DOSBox with Visual Studio

2018-07-14T00:41:34Z

Rainwarrior: probably worth warning about the current debugging situation because this is a severe problem

Building DOSBox with MinGW

2018-07-14T00:37:12Z

Rainwarrior: /* Compiling DOSBox */ that last line is another step

DOSBox is a complicated project. This document aims to provide a step by step description of how to use the MinGW developement environment to successfully build DOSBox. An alternative is to use [[Building DOSBox with Visual Studio|Microsoft Visual Studio]].

This page will guide you through setting up MinGW to compile a current (SVN/CVS) version of DOSBox. Because of updates to compilers and libraries, this guide will not work with the 0.74 (the last official release, which is currently over 6 years old) source files.

An alternative guide is also available on the forums: https://www.vogons.org/viewtopic.php?f=31&t=55706

Additional build setup notes may be found in the latest '''INSTALL''' file: https://sourceforge.net/p/dosbox/code-0/HEAD/tree/dosbox/trunk/INSTALL

== Installing MinGW ==
* Download mingw-get-setup.exe from http://sourceforge.net/projects/mingw/
* Run the installer, choosing the defaults
* Once the '''MinGW Installation Manager''' application starts, select
** mingw-developer-toolkit (msys-base should be automatically added)
** mingw32-base
** mingw32-gcc-g++
* On the installation menu, apply changes, and confirm that you want to apply the changes

The installation manager is going to download a bunch of files, and at the end, start installing them. Once this is done, you can close the dialog box as well as the installation manager.

Well done, MinGW is now installed! Let's start it up.

* Browse to '''C:\MinGW\msys\1.0'''
* Run '''MSYS.BAT'''

This will start up a DOS prompt like screen, lets mount the base path
mount 'c:\MinGW' /mingw

You have now completed this section, lets move on to adding the SDL libraries to MinGW.

== Adding the SDL libraries to MinGW ==
* Download the pre compiled SDL development libraries from here http://www.libsdl.org/release/SDL-devel-1.2.15-mingw32.tar.gz
* Copy the downloaded file to your MSYS home folder, it's going to be something like '''C:\MinGW\msys\1.0\home\Administrator'''
* Switch back to the MSYS command prompt we started earlier
* Lets extract the downloaded files
tar xvf SDL-devel-1.2.15-mingw32.tar.gz
* And now add the files to MinGW
cd SDL-1.2.15
make install-sdl prefix=/mingw
cd ..

Cool, the SDL libraries have been added to MinGW, onto the next section.

== Adding Direct Draw support to DOSBox (Optional) ==
If you want to give DOSBox the option to use the DDRAW output option, then we need to add a couple of extra libraries to MinGW
* Download the following file, http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the files (the -C parameter, tells tar where to extract the files to)
tar xvf directx-devel.tar.gz -C /mingw

== Adding networking support to DOSBox (Optional) ==
These steps show you how to add the SDL_net libraries to MinGW, which enable networking and modem for DOSBox. If you aren't going to be using DOSBox for multi player games, then you can probably skip this step.
* Download the SDL_net source files from https://www.libsdl.org/projects/SDL_net/release/SDL_net-1.2.8.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_net-1.2.8.tar.gz
* Lets configure the libraries
cd SDL_net-1.2.8
./configure --prefix=/mingw
* '''SDLnet.c''' will have to be modified slightly to compile. Open it with a text editor and add the following #include near the top of the file:
#include <winerror.h>
* And now compile them
make
* And then install them (copy the files)
make install
cd ..

== Adding screenshot support (Optional) ==
This one is a bit tricky because it relies on two libraries, zlib (libpng needs these libraries), and libpng. We are also going to be compiling the libraries statically to keep external DLL's to a minimum.
* Download zlib from here http://sourceforge.net/projects/libpng/files/zlib/1.2.8/zlib-1.2.8.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf zlib-1.2.8.tar.xz
* Lets build the static library
cd zlib-1.2.8
make -f win32/Makefile.gcc
* And now copy the files to /mingw
cp libz.a /mingw/lib/
cp zlib.h zconf.h /mingw/include/
cd ..
Cool, that wasn't too hard, onto libpng
* Download libpng from here https://sourceforge.net/projects/libpng/files/libpng16/older-releases/1.6.18/libpng-1.6.18.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libpng-1.6.18.tar.xz
* Configure the library
cd libpng-1.6.18
./configure --disable-shared --prefix=/mingw
* There is currently [https://sourceforge.net/p/libpng/bugs/273/ a problem with the configure script] that will need to be manually resolved. Open '''pnglibconf.h''' with a text editor, and you will find several #define lines near the bottom that have been erroneously split into two lines. This can be fixed by adding a backslash to the end of the affected lines:
199: #define PNG_TEXT_Z_DEFAULT_COMPRESSION \
201: #define PNG_TEXT_Z_DEFAULT_STRATEGY \
209: #define PNG_ZLIB_VERNUM \
211: #define PNG_Z_DEFAULT_COMPRESSION \
213: #define PNG_Z_DEFAULT_NOFILTER_STRATEGY \
215: #define PNG_Z_DEFAULT_STRATEGY \
* And now to compile and install the files
make
make install
cd ..

== Adding support for compressed audio on diskimages (Optional) ==
This is for cue/bin cdrom images with compressed (ogg) audio tracks. We will be adding the libvorbis, libogg, and sdl_sound libraries.
* Download libogg from here http://downloads.xiph.org/releases/ogg/libogg-1.3.2.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libogg-1.3.2.tar.gz
* Configure the library, disabling shared library files
cd libogg-1.3.2
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download libvorbis from here http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.5.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libvorbis-1.3.5.tar.gz
* Configure the library, disabling shared library files
cd libvorbis-1.3.5
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download sdl_sound from here https://www.icculus.org/SDL_sound/downloads/SDL_sound-1.0.3.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_sound-1.0.3.tar.gz
* Configure and compile
cd SDL_sound-1.0.3
./configure --disable-shared --prefix=/mingw LIBS="-lvorbisfile -lvorbis -logg"
make
make install
cd ..

== Enabling the debugger (You probably don't want this) ==
The debugger is mainly for developers of DOSBox, so they can find out why a game isn't working.
* Download the PDCurses source files from http://sourceforge.net/projects/pdcurses/files/pdcurses/3.4/PDCurses-3.4.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf PDCurses-3.4.tar.gz
* Compile the library
cd PDCurses-3.4/win32
make -f gccwin32.mak DLL=N
* And now copy the files to your /mingw folders
cp pdcurses.a /mingw/lib/libpdcurses.a
cd ..
cp curses.h panel.h /mingw/include/
cd ..

== Compiling DOSBox ==
* If you plan on rebuilding periodically with the latest code, you can check out the Subversion repository here: https://sourceforge.net/p/dosbox/code-0/HEAD/tree/dosbox/trunk/
* Otherwise you can download a snapshot of the latest DOSBox SVN source here: http://source.dosbox.com/dosboxsvn.tgz
* See also [[SVN Builds]] for a list of unofficial alternative versions of DOSBox that you may wish to try instead. Many of them have additional features.

* If using the snapshot, copy that file to your MSYS home folder, and extract the file
tar xvf dosboxsvn.tgz
* Let's configure DOSBox, and tell it to use the static C library (-static-libgcc) and C++ library (-static-libstdc++) and stripping the final EXE of debug information (-s)
cd dosbox
./autogen.sh
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s"
* For SDL_sound support, you have to extra some extra parameters so that the configure command knows where to find the audio library files (LIBS="-lvorbisfile.....)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg"
* If you want to enable debugging (you probably don't)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg" --enable-debug
* And now for compiling DOSBox
make
* The last step is to gather all the files together in a folder
** Create a folder with a name of your choosing
** Copy the dosbox.exe file located under the '''dosbox\src''' folder, e.g. '''C:\MinGW\msys\1.0\home\Administrator\dosbox\src''' to the folder you created
** Copy the SDL.dll file located under '''SDL-1.2.15\bin''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL-1.2.15\bin''' to the folder you created
** Optionally, copy the SDL_net.dll file located under '''SDL_net-1.2.8\.libs''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL_net-1.2.8\.libs''' to the folder you created

* Start up DOSBox, and see if it works!

Building DOSBox with Visual Studio

2018-07-14T00:35:07Z

Rainwarrior: /* Build DOSBox */ formatting

Building DOSBox with Visual Studio

2018-07-14T00:29:52Z

Rainwarrior: /* Build DOSBox */ unfinished sentence

Building DOSBox with Visual Studio

2018-07-14T00:28:03Z

Rainwarrior: removing rest of outdated guide

Building DOSBox with Visual Studio

2018-07-14T00:27:09Z

Rainwarrior: how to get and build DOSBox

While the official Windows build environment for DOSBox is [[Building DOSBox with MinGW|MinGW]], it may also be built in Visual Studio for users more comfortable with this.

== Get Visual Studio ==
Free versions of Visual Studio are available at: https://visualstudio.microsoft.com/

The free version of Visual Studio 2017 is called the "Community" edition. Prior to this (VS2005-2015) free versions were called the "Express" edition.

Some older versions are available at: https://visualstudio.microsoft.com/vs/older-downloads/

When installing Visual Studio, there may be tools for multiple languages available (C++, C#, Visual Basic .NET, Java, etc.) but only the C++ tools are necessary for DOSBox.

== Get Libraries ==

* Required: [https://www.libsdl.org/download-1.2.php '''SDL 1.2''']
** https://www.libsdl.org/release/SDL-devel-1.2.15-VC.zip (VS2013 or earlier)
** https://www.libsdl.org/release/SDL-1.2.15.zip (VS2015 or later)

* Optional for screenshots and video capture:
** [https://zlib.net/ '''zlib'''] - https://zlib.net/fossils/zlib-1.2.8.tar.gz
** [http://www.libpng.org/pub/png/libpng.html '''libpng'''] - https://download.sourceforge.net/libpng/lpng1634.zip

* Optional for networking:
** [https://www.libsdl.org/projects/SDL_net/release-1.2.html '''SDL_net 1.2'''] - https://www.libsdl.org/projects/SDL_net/release/SDL_net-devel-1.2.8-VC.zip

* Optional for compressed audio disc images:
** [https://www.icculus.org/SDL_sound/ '''SDL_sound''']

* Optional for DOS debugging tools:
** [https://pdcurses.sourceforge.io/ '''PDCurses''']

== Prepare Libraries ==

=== SDL ===
If using VS2013 or earlier, you can use the pre-built library in '''SDL-devel-1.2.15-VC.zip'''. For VS2015 or later you will need to rebuild it from source ('''SDL-1.2.15.zip'''):
* Open '''SDL-1.2.15\VisualC\SDL.sln''' and allow Visual Studio to automatically convert the solution and project to the latest version.
* Select the ''Release'' configuration and use the ''Build'' menu to build the solution.
* The following 3 files should be built:
** '''SDL-1.2.15\VisualC\Release\SDL.dll'''
** '''SDL-1.2.15\VisualC\Release\SDL.lib'''
** '''SDL-1.2.15\VisualC\SDLmain\Release\SDLmain.lib'''
* The following folder also contains relevant include files for the library:
** '''SDL-1.2.15\include'''
* If you need more info on building SDL with VS, see: '''SDL-1.2.15\VisualC.html'''

=== zlib / libpng (optional) ===
Enables screenshot and video capture.

Because '''zlib''' is a dependency of '''libpng''', a VS solution to build both at once is provided by the ''libpng'' package.

* Unpack '''lpng1634.zip''' to create the folder: '''lpng1634'''
* Unpack '''zlib-1.2.8.tar.gz''' to create an adjacent folder: '''zlib-1.2.8'''
* Open '''lpng1634\projects\vstudio\zlib.props''' with a text editor.
** Near the bottom of the file you will find '''<DisableSpecificWarnings>'''. Add ''';5045''' to the end of this list. (This disables a new spurious warning in VS2017.)
* Open '''lpng1634\projects\vstudio\vstudio.sln''' and allow Visual Studio to automatically convert the solution and projects to the latest version.
* Select the '''Release Library''' configuration.
* Right click on the '''zlib''' project in the solution explorer and open its '''Properties'''.
** From '''Configuration Properties > C/C++ > Preprocessor > Preprocessor Definitions''' remove '''Z_SOLO'''. (Currently causes video capture to fail and crash.)
** Change '''Configuration Properties > C/C++ > Code Generation > Runtime Library''' to '''Multi-threaded DLL (/MD)'''.
* Right click on the '''zlib''' project and build it.
* Now open the '''libpng''' project's properties.
** Change '''Configuration Properties > C/C++ > Code Generation > Runtime Library''' to '''Multi-threaded DLL (/MD)'''.
* Build the '''libpng''' project.
* The following libraries should now be built:
** '''lpng1634\projects\vstudio\Release Library\zlib.lib'''
** '''lpng1634\projects\vstudio\Release Library\libpng16.lib'''
* Include folders:
** '''lpng1634'''
** '''zlib-1.2.8'''
* For more libpng build information see: '''lpng1634\INSTALL'''

=== SDL_net (optional) ===
Enables networking.

You can use the pre-built libraries in '''SDL_net-devel-1.2.8-VC.zip'''.
* Library files:
** '''SDL_net-1.2.8\lib\x86\SDL_net.dll'''
** '''SDL_net-1.2.8\lib\x86\SDL_net.lib'''
* Include folder:
** '''SDL_net-1.2.8\include'''

=== SDL_sound (optional) ===
Enables the use of CD images with compressed audio.
* Guide not yet written.

=== PDCurses (optional) ===
Enables a DOS debugger.
* Guide not yet written.

== Get DOSBox Source ==
* If you plan on rebuilding periodically with the latest code, you can check out the Subversion repository here: https://sourceforge.net/p/dosbox/code-0/HEAD/tree/dosbox/trunk/
* Otherwise you can download a snapshot of the latest DOSBox SVN source here: http://source.dosbox.com/dosboxsvn.tgz
* See also [[SVN Builds]] for a list of unofficial alternative versions of DOSBox that you may wish to try instead. Many of them have additional features.

== Build DOSBox ==
* After downloading the source code, open the Visual Studio solution: '''dosbox\visualc_net\dosbox.sln'''
* Allow it to automatically convert to the latest version.
* Right click the '''dosbox''' project in the Solution Explorer and open its '''Properties'''.
** When editing the properties, edits will have to be made for each configuration you may want to build. In the top left there is an option for '''Debug''', '''Release''' and '''All Configurations'''. The Release build is most commonly used, but
** Click the drop down triangle on '''Configuration Properties > C/C++ > General > Additional Include Directories''' and edit this list. Add the appropriate '''include path''' for each library prepared above. Keep in mind that paths are relative to the '''dosbox\visualc_net''' folder.
** Edit '''Configuration Properties > Linker > General > Additional Library Directories''' and add the path to each library (.lib) file prepared above.
** Edit '''Configuration Properties > Linker > Input > Additional Dependencies''' to add or remove libraries. (You will have to select either the Debug or Release configuration for this, as the Debug build uses a different list of libraries than the Release.)
*** Remove '''zlib.lib''' and '''libpng.lib''' if not using these. Rename '''libpng.lib''' as '''libpng16.lib''' if you are using it.
*** Remove '''sdl_net.lib''' if not using it.
*** Add an entry for SDL_sound if using it.
*** Remove '''curses.lib''' if not using it.
* Find '''dosbox\src\platform\visualc\config.h''' and open it (in the solution explorer it is under '''dosbox \ Source Files \ visualc''').
** '''C_SSHOT''' to 0 if not using zlib/libpng.
** '''C_MODEM''' and '''C_IPX''' to 0 if not using SDL_net.
** Add '''#define C_SDL_SOUND''' if using SDL_sound.
** '''C_DEBUG''' to 1 if using the PDCurses.
* After all of this is set up, you may build the '''dosbox''' project. Choose a Debug or Release configuration (recommend: Release) and use the build menu to build the solution. One of the following will be built:
** '''dosbox\visualc_net\Release\dosbox.exe'''
** '''dosbox\visualc_net\Debug\dosbox.exe'''
* Finally, take the '''SDL.dll''' and '''SDL_net.dll''' files prepared above and place them in the same directory as '''dosbox.exe'''. It should now be ready to run.

== Set up the environment ==
[[Image:Vce_guide1.png|thumb|Setting the include directories for SDL]]
From your start menu, start VCE. After a few moments, the IDE (Integrated Development Environment) will start. The first thing we need to do is tell VCE where to find SDL. From the "Tools" menu select "Options". When the Options menu appears, expand the category "Projects and Solutions" and choose "VC++ Directories". From the directories pulldown, choose to show the directories for include files, click the folder icon and add the folder for the SDL includes. If you have been following this guide literally, that would <tt>C:\Development\SDL-1.2.13\include</tt>. Next, elect to show the directories for library files. This time, add the folder for the SDL libraries. When you have followed this guide, that would be <tt>C:\Development\SDL-1.2.13\lib</tt>.

After you have done this, click OK to accept and close the options.

 
== Set up the solution ==
=== Conversion wizard ===
[[Image:Vce_guide2.png|thumb|Conversion wizard]]
Open the solution provided by DOSBox. It can be found as <tt>C:\Development\dosbox\visualc_net\dosbox.sln</tt>. If you have file extensions hidden (as they are by default), you may select "Solution files (*.sln)" from the object type dropdown to ensure you get the correct one. The first time you open the solution, VCE will present you with the Visual Studio Conversion Wizard, because the solution included in the DOSBox distribution is for an older version of Visual C++. You can simply click Finish and be done with it. If you want, you can take a look at the conversion log, but the information in there is not particularly interesting.
 
=== Dependencies ===
[[Image:Vce_guide3.png|thumb|Editing the additional dependencies]]
Now that the solution has been opened, it is necessary to disable some of the optional features of DOSBox. From the "Project" menu select "dosbox Properties". Expand the "Configuration Properties" and then the "Linker" category. Then choose "Input". From the properties on the right, you will need to remove some of the "Additional Dependencies". With the setup I have described here, I need to remove '''sdl_net.lib''', '''zlib.lib''', '''libpng.lib''' and '''curses.lib''' (you will also not need the odbc32.lib and odbccp32.lib references, but there is no harm in leaving them). Apply the changes and use the dropdown at the top left to switch to the Release configuration. Repeat the previous step, removing those same references and again apply the changes.
 
=== Configuration setup ===
[[Image:Vce_guide4.png|thumb|Adjusting the config.h file]]
In the Solution Explorer, browse down the solution into "Source files" and then "visualc". Open the file <tt>config.h</tt> listed there and do some editing. Find the line that reads
#define C_SSHOT 1
and change the 1 to a 0. Do the same for the lines mentioning <tt>C_MODEM</tt> and <tt>C_IPX</tt>. The reason we are disabling these options is that they require some extra libraries that we haven’t set up for this tutorial. Also, set <tt>C_CORE_INLINE</tt> to 1 to enable faster CPU emulation.

In the Solution Explorer, in the "Source files", you will find the file <tt>winres.rc</tt>. Right-click on that and choose "View code". ''Remove'' the line at the top that reads
#include "afxres.h"
When you have done this, save the solution ("Save all" from the file menu). This ensures you won’t have to repeat any of the previous steps.
 

== The actual build ==
[[Image:Vce_guide5.png|thumb|Build successfully completed]]
Before building, right click on "Solution 'dosbox'" in the Solution Explorer and go to Properties -> Configuration Properties. Set the Configuration dropdown box to "Release" instead of "Debug". This will cause VC++ to build an optimized binary without extra debug features.

Now that all this is done, press F7 to start the build process. There will be a few warnings, but they are unimportant. The build may take a few minutes depending on the speed of your computer, but if you have followed this tutorial it will complete successfully.

Note that to actually run the executable you have built, you will need the SDL library (<tt>SDL.DLL</tt>) from your regular DOSBox install and place it in the <tt>C:\Development\dosbox\visualc_net</tt> directory.

SVN Builds

2018-07-13T23:31:24Z

Rainwarrior: /* Enhanced SVN builds */ dosbox-patched appears to be updated daily

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.

The official DOSBox SVN repository is hosted at sourceforge.net:
: https://sourceforge.net/projects/dosbox/

==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 [http://www.sourceforge.net/ sourceforge.net] 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. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release (0.74) is several years old, and is therefore missing a significant amount of work performed by the developers. 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 [http://www.vogons.org/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 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 [http://www.vogons.org/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? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 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:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.12 (ppc/intel)
** URL: https://www.dropbox.com/s/kbrf5elbcu66kst/Dosbox-Snapshot.dmg?dl=1
** Notes: Automatically updated on changes to SVN.

* '''Yesterplay 80''' for Windows and Linux
** URL: https://blog.yesterplay80.net/dosbox-ece-en/
** Notes: Also provides a modified DOSBox ECE (Enhanced Community Edition) build.

===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 SVN-lfn''' (DOSBox with Long File Name (LFN), mouse copy/paste support and more) by Wengier
** Last updated: 2017-09-20
** SVN base version: r4052
** URL: http://www.wpdos.org/dosbox-vdos-lfn.html (introduction + source + Windows binary + links to forum discussions)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** URL: http://bit.ly/1laDvGX (alternative Windows binary compiled with MinGW instead of Visual Studio, zipped)
** Description: This is an enhanced build of DOSBox based on its SVN version that adds features like Windows-style Long File Name (LFN) and mouse copy/paste support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). It now also includes features such as automatic drive mounting, improved command-line handling, APM power off, direct parallel port passthrough used for printing, DOS APIs that communicate with the Windows clipboard, and DBCS support for displaying CJK (East Asian) characters. Windows binaries are provided, but sources should work on other platforms such as Linux and macOS/OS X too (pdcurses might be required for the cross-platform clipboard copy/paste feature). Please see README.TXT file inside the binary package for more information.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: Daily
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The last version broke this build in various places and uses out of date and not fully working changes of the DOSBox-X branch. It is no longer recommended to use it.The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** 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: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** 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 sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/4052/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2017-09-20'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===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:
* [[BuildingDOSBox]]

===Unofficial ports===
The following DOSBoxWiki article discusses unofficial ports for other operating systems, which are not in any way supported by the DOSBox team.
* [[Unofficial ports]]

===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) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* https://sourceforge.net/p/dosbox/code-0/HEAD/tree/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

SVN Builds

2018-07-13T23:29:08Z

Rainwarrior: /* List of SVN Builds */ another vanilla build that seems to be frequently updated and more usable than EmuCR's

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.

The official DOSBox SVN repository is hosted at sourceforge.net:
: https://sourceforge.net/projects/dosbox/

==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 [http://www.sourceforge.net/ sourceforge.net] 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. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release (0.74) is several years old, and is therefore missing a significant amount of work performed by the developers. 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 [http://www.vogons.org/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 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 [http://www.vogons.org/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? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 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:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.12 (ppc/intel)
** URL: https://www.dropbox.com/s/kbrf5elbcu66kst/Dosbox-Snapshot.dmg?dl=1
** Notes: Automatically updated on changes to SVN.

* '''Yesterplay 80''' for Windows and Linux
** URL: https://blog.yesterplay80.net/dosbox-ece-en/
** Notes: Also provides a modified DOSBox ECE (Enhanced Community Edition) build.

===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 SVN-lfn''' (DOSBox with Long File Name (LFN), mouse copy/paste support and more) by Wengier
** Last updated: 2017-09-20
** SVN base version: r4052
** URL: http://www.wpdos.org/dosbox-vdos-lfn.html (introduction + source + Windows binary + links to forum discussions)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** URL: http://bit.ly/1laDvGX (alternative Windows binary compiled with MinGW instead of Visual Studio, zipped)
** Description: This is an enhanced build of DOSBox based on its SVN version that adds features like Windows-style Long File Name (LFN) and mouse copy/paste support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). It now also includes features such as automatic drive mounting, improved command-line handling, APM power off, direct parallel port passthrough used for printing, DOS APIs that communicate with the Windows clipboard, and DBCS support for displaying CJK (East Asian) characters. Windows binaries are provided, but sources should work on other platforms such as Linux and macOS/OS X too (pdcurses might be required for the cross-platform clipboard copy/paste feature). Please see README.TXT file inside the binary package for more information.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The last version broke this build in various places and uses out of date and not fully working changes of the DOSBox-X branch. It is no longer recommended to use it.The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** 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: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** 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 sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/4052/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2017-09-20'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===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:
* [[BuildingDOSBox]]

===Unofficial ports===
The following DOSBoxWiki article discusses unofficial ports for other operating systems, which are not in any way supported by the DOSBox team.
* [[Unofficial ports]]

===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) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* https://sourceforge.net/p/dosbox/code-0/HEAD/tree/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

Building DOSBox with Visual Studio

2018-07-13T22:36:01Z

Rainwarrior: /* zlib / libpng (optional) */ ' mismatch

While the official Windows build environment for DOSBox is [[Building DOSBox with MinGW|MinGW]], it may also be built in Visual Studio for users more comfortable with this.

== Get Visual Studio ==
Free versions of Visual Studio are available at: https://visualstudio.microsoft.com/

The free version of Visual Studio 2017 is called the "Community" edition. Prior to this (VS2005-2015) free versions were called the "Express" edition.

Some older versions are available at: https://visualstudio.microsoft.com/vs/older-downloads/

When installing Visual Studio, there may be tools for multiple languages available (C++, C#, Visual Basic .NET, Java, etc.) but only the C++ tools are necessary for DOSBox.

== Get Libraries ==

* Required: [https://www.libsdl.org/download-1.2.php '''SDL 1.2''']
** https://www.libsdl.org/release/SDL-devel-1.2.15-VC.zip (VS2013 or earlier)
** https://www.libsdl.org/release/SDL-1.2.15.zip (VS2015 or later)

* Optional for screenshots and video capture:
** [https://zlib.net/ '''zlib'''] - https://zlib.net/fossils/zlib-1.2.8.tar.gz
** [http://www.libpng.org/pub/png/libpng.html '''libpng'''] - https://download.sourceforge.net/libpng/lpng1634.zip

* Optional for networking:
** [https://www.libsdl.org/projects/SDL_net/release-1.2.html '''SDL_net 1.2'''] - https://www.libsdl.org/projects/SDL_net/release/SDL_net-devel-1.2.8-VC.zip

* Optional for compressed audio disc images:
** [https://www.icculus.org/SDL_sound/ '''SDL_sound''']

* Optional for DOS debugging tools:
** [https://pdcurses.sourceforge.io/ '''PDCurses''']

== Prepare Libraries ==

=== SDL ===
If using VS2013 or earlier, you can use the pre-built library in '''SDL-devel-1.2.15-VC.zip'''. For VS2015 or later you will need to rebuild it from source ('''SDL-1.2.15.zip'''):
* Open '''SDL-1.2.15\VisualC\SDL.sln''' and allow Visual Studio to automatically convert the solution and project to the latest version.
* Select the ''Release'' configuration and use the ''Build'' menu to build the solution.
* The following 3 files should be built:
** '''SDL-1.2.15\VisualC\Release\SDL.dll'''
** '''SDL-1.2.15\VisualC\Release\SDL.lib'''
** '''SDL-1.2.15\VisualC\SDLmain\Release\SDLmain.lib'''
* The following folder also contains relevant include files for the library:
** '''SDL-1.2.15\include'''
* If you need more info on building SDL with VS, see: '''SDL-1.2.15\VisualC.html'''

=== zlib / libpng (optional) ===
Enables screenshot and video capture.

Because '''zlib''' is a dependency of '''libpng''', a VS solution to build both at once is provided by the ''libpng'' package.

* Unpack '''lpng1634.zip''' to create the folder: '''lpng1634'''
* Unpack '''zlib-1.2.8.tar.gz''' to create an adjacent folder: '''zlib-1.2.8'''
* Open '''lpng1634\projects\vstudio\zlib.props''' with a text editor.
** Near the bottom of the file you will find '''<DisableSpecificWarnings>'''. Add ''';5045''' to the end of this list. (This disables a new spurious warning in VS2017.)
* Open '''lpng1634\projects\vstudio\vstudio.sln''' and allow Visual Studio to automatically convert the solution and projects to the latest version.
* Select the '''Release Library''' configuration.
* Right click on the '''zlib''' project in the solution explorer and open its '''Properties'''.
** From '''Configuration Properties > C/C++ > Preprocessor > Preprocessor Definitions''' remove '''Z_SOLO'''. (Currently causes video capture to fail and crash.)
** Change '''Configuration Properties > C/C++ > Code Generation > Runtime Library''' to '''Multi-threaded DLL (/MD)'''.
* Right click on the '''zlib''' project and build it.
* Now open the '''libpng''' project's properties.
** Change '''Configuration Properties > C/C++ > Code Generation > Runtime Library''' to '''Multi-threaded DLL (/MD)'''.
* Build the '''libpng''' project.
* The following libraries should now be built:
** '''lpng1634\projects\vstudio\Release Library\zlib.lib'''
** '''lpng1634\projects\vstudio\Release Library\libpng16.lib'''
* Include folders:
** '''lpng1634'''
** '''zlib-1.2.8'''
* For more libpng build information see: '''lpng1634\INSTALL'''

=== SDL_net (optional) ===
Enables networking.

You can use the pre-built libraries in '''SDL_net-devel-1.2.8-VC.zip'''.
* Library files:
** '''SDL_net-1.2.8\lib\x86\SDL_net.dll'''
** '''SDL_net-1.2.8\lib\x86\SDL_net.lib'''
* Include folder:
** '''SDL_net-1.2.8\include'''

=== SDL_sound (optional) ===
Enables the use of CD images with compressed audio.
* Guide not yet written.

=== PDCurses (optional) ===
Enables a DOS debugger.
* Guide not yet written.

== Get the DOSBox sources ==
The next step is to get DOSBox itself. At the time of writing, the latest official release of DOSBox is 0.74, available at the [[Releases]] page. However, it was released over 6 years ago, so if you want more recent source code you can go to the [[SVN Builds]] page to download the source of some SVN version of DOSBox. Since the DOSBox sources come as a <tt>.tar.gz</tt> file, you may need a separate program to extract this. Unpack the source to the location of your choosing. For this discussion, I have chosen <tt>C:\Development\dosbox</tt>.

== Set up the environment ==
[[Image:Vce_guide1.png|thumb|Setting the include directories for SDL]]
From your start menu, start VCE. After a few moments, the IDE (Integrated Development Environment) will start. The first thing we need to do is tell VCE where to find SDL. From the "Tools" menu select "Options". When the Options menu appears, expand the category "Projects and Solutions" and choose "VC++ Directories". From the directories pulldown, choose to show the directories for include files, click the folder icon and add the folder for the SDL includes. If you have been following this guide literally, that would <tt>C:\Development\SDL-1.2.13\include</tt>. Next, elect to show the directories for library files. This time, add the folder for the SDL libraries. When you have followed this guide, that would be <tt>C:\Development\SDL-1.2.13\lib</tt>.

After you have done this, click OK to accept and close the options.

 
== Set up the solution ==
=== Conversion wizard ===
[[Image:Vce_guide2.png|thumb|Conversion wizard]]
Open the solution provided by DOSBox. It can be found as <tt>C:\Development\dosbox\visualc_net\dosbox.sln</tt>. If you have file extensions hidden (as they are by default), you may select "Solution files (*.sln)" from the object type dropdown to ensure you get the correct one. The first time you open the solution, VCE will present you with the Visual Studio Conversion Wizard, because the solution included in the DOSBox distribution is for an older version of Visual C++. You can simply click Finish and be done with it. If you want, you can take a look at the conversion log, but the information in there is not particularly interesting.
 
=== Dependencies ===
[[Image:Vce_guide3.png|thumb|Editing the additional dependencies]]
Now that the solution has been opened, it is necessary to disable some of the optional features of DOSBox. From the "Project" menu select "dosbox Properties". Expand the "Configuration Properties" and then the "Linker" category. Then choose "Input". From the properties on the right, you will need to remove some of the "Additional Dependencies". With the setup I have described here, I need to remove '''sdl_net.lib''', '''zlib.lib''', '''libpng.lib''' and '''curses.lib''' (you will also not need the odbc32.lib and odbccp32.lib references, but there is no harm in leaving them). Apply the changes and use the dropdown at the top left to switch to the Release configuration. Repeat the previous step, removing those same references and again apply the changes.
 
=== Configuration setup ===
[[Image:Vce_guide4.png|thumb|Adjusting the config.h file]]
In the Solution Explorer, browse down the solution into "Source files" and then "visualc". Open the file <tt>config.h</tt> listed there and do some editing. Find the line that reads
#define C_SSHOT 1
and change the 1 to a 0. Do the same for the lines mentioning <tt>C_MODEM</tt> and <tt>C_IPX</tt>. The reason we are disabling these options is that they require some extra libraries that we haven’t set up for this tutorial. Also, set <tt>C_CORE_INLINE</tt> to 1 to enable faster CPU emulation.

In the Solution Explorer, in the "Source files", you will find the file <tt>winres.rc</tt>. Right-click on that and choose "View code". ''Remove'' the line at the top that reads
#include "afxres.h"
When you have done this, save the solution ("Save all" from the file menu). This ensures you won’t have to repeat any of the previous steps.
 

== The actual build ==
[[Image:Vce_guide5.png|thumb|Build successfully completed]]
Before building, right click on "Solution 'dosbox'" in the Solution Explorer and go to Properties -> Configuration Properties. Set the Configuration dropdown box to "Release" instead of "Debug". This will cause VC++ to build an optimized binary without extra debug features.

Now that all this is done, press F7 to start the build process. There will be a few warnings, but they are unimportant. The build may take a few minutes depending on the speed of your computer, but if you have followed this tutorial it will complete successfully.

Note that to actually run the executable you have built, you will need the SDL library (<tt>SDL.DLL</tt>) from your regular DOSBox install and place it in the <tt>C:\Development\dosbox\visualc_net</tt> directory.

Building DOSBox with Visual Studio

2018-07-13T22:32:16Z

Rainwarrior: /* Prepare Libraries */ how to prepare libpng/zlib

While the official Windows build environment for DOSBox is [[Building DOSBox with MinGW|MinGW]], it may also be built in Visual Studio for users more comfortable with this.

== Get Visual Studio ==
Free versions of Visual Studio are available at: https://visualstudio.microsoft.com/

The free version of Visual Studio 2017 is called the "Community" edition. Prior to this (VS2005-2015) free versions were called the "Express" edition.

Some older versions are available at: https://visualstudio.microsoft.com/vs/older-downloads/

When installing Visual Studio, there may be tools for multiple languages available (C++, C#, Visual Basic .NET, Java, etc.) but only the C++ tools are necessary for DOSBox.

== Get Libraries ==

* Required: [https://www.libsdl.org/download-1.2.php '''SDL 1.2''']
** https://www.libsdl.org/release/SDL-devel-1.2.15-VC.zip (VS2013 or earlier)
** https://www.libsdl.org/release/SDL-1.2.15.zip (VS2015 or later)

* Optional for screenshots and video capture:
** [https://zlib.net/ '''zlib'''] - https://zlib.net/fossils/zlib-1.2.8.tar.gz
** [http://www.libpng.org/pub/png/libpng.html '''libpng'''] - https://download.sourceforge.net/libpng/lpng1634.zip

* Optional for networking:
** [https://www.libsdl.org/projects/SDL_net/release-1.2.html '''SDL_net 1.2'''] - https://www.libsdl.org/projects/SDL_net/release/SDL_net-devel-1.2.8-VC.zip

* Optional for compressed audio disc images:
** [https://www.icculus.org/SDL_sound/ '''SDL_sound''']

* Optional for DOS debugging tools:
** [https://pdcurses.sourceforge.io/ '''PDCurses''']

== Prepare Libraries ==

=== SDL ===
If using VS2013 or earlier, you can use the pre-built library in '''SDL-devel-1.2.15-VC.zip'''. For VS2015 or later you will need to rebuild it from source ('''SDL-1.2.15.zip'''):
* Open '''SDL-1.2.15\VisualC\SDL.sln''' and allow Visual Studio to automatically convert the solution and project to the latest version.
* Select the ''Release'' configuration and use the ''Build'' menu to build the solution.
* The following 3 files should be built:
** '''SDL-1.2.15\VisualC\Release\SDL.dll'''
** '''SDL-1.2.15\VisualC\Release\SDL.lib'''
** '''SDL-1.2.15\VisualC\SDLmain\Release\SDLmain.lib'''
* The following folder also contains relevant include files for the library:
** '''SDL-1.2.15\include'''
* If you need more info on building SDL with VS, see: '''SDL-1.2.15\VisualC.html'''

=== zlib / libpng (optional) ===
Enables screenshot and video capture.

Because '''zlib''' is a dependency of '''libpng''', a VS solution to build both at once is provided by the ''libpng'' package.

* Unpack '''lpng1634.zip''' to create the folder: '''lpng1634'''
* Unpack '''zlib-1.2.8.tar.gz''' to create an adjacent folder: '''zlib-1.2.8'''
* Open '''lpng1634\projects\vstudio\zlib.props''' with a text editor.
** Near the bottom of the file you will find '''<DisableSpecificWarnings>'''. Add ''';5045''' to the end of this list. (This disables a new spurious warning in VS2017.)
* Open '''lpng1634\projects\vstudio\vstudio.sln''' and allow Visual Studio to automatically convert the solution and projects to the latest version.
* Select the '''Release Library''' configuration.
* Right click on the '''zlib''' project in the solution explorer and open its '''Properties'''.
** From '''Configuration Properties > C/C++ > Preprocessor > Preprocessor Definitions''' remove '''Z_SOLO'''. (Currently causes video capture to fail and crash.)
** Change '''Configuration Properties > C/C++ > Code Generation > Runtime Library''' to '''Multi-threaded DLL (/MD)'''.
* Right click on the '''zlib'' project and build it.
* Now open the '''libpng''' project's properties.
** Change '''Configuration Properties > C/C++ > Code Generation > Runtime Library''' to '''Multi-threaded DLL (/MD)'''.
* Build the '''libpng''' project.
* The following libraries should now be built:
** '''lpng1634\projects\vstudio\Release Library\zlib.lib'''
** '''lpng1634\projects\vstudio\Release Library\libpng16.lib'''
* Include folders:
** '''lpng1634'''
** '''zlib-1.2.8'''
* For more libpng build information see: '''lpng1634\INSTALL'''

=== SDL_net (optional) ===
Enables networking.

You can use the pre-built libraries in '''SDL_net-devel-1.2.8-VC.zip'''.
* Library files:
** '''SDL_net-1.2.8\lib\x86\SDL_net.dll'''
** '''SDL_net-1.2.8\lib\x86\SDL_net.lib'''
* Include folder:
** '''SDL_net-1.2.8\include'''

=== SDL_sound (optional) ===
Enables the use of CD images with compressed audio.
* Guide not yet written.

=== PDCurses (optional) ===
Enables a DOS debugger.
* Guide not yet written.

== Get the DOSBox sources ==
The next step is to get DOSBox itself. At the time of writing, the latest official release of DOSBox is 0.74, available at the [[Releases]] page. However, it was released over 6 years ago, so if you want more recent source code you can go to the [[SVN Builds]] page to download the source of some SVN version of DOSBox. Since the DOSBox sources come as a <tt>.tar.gz</tt> file, you may need a separate program to extract this. Unpack the source to the location of your choosing. For this discussion, I have chosen <tt>C:\Development\dosbox</tt>.

== Set up the environment ==
[[Image:Vce_guide1.png|thumb|Setting the include directories for SDL]]
From your start menu, start VCE. After a few moments, the IDE (Integrated Development Environment) will start. The first thing we need to do is tell VCE where to find SDL. From the "Tools" menu select "Options". When the Options menu appears, expand the category "Projects and Solutions" and choose "VC++ Directories". From the directories pulldown, choose to show the directories for include files, click the folder icon and add the folder for the SDL includes. If you have been following this guide literally, that would <tt>C:\Development\SDL-1.2.13\include</tt>. Next, elect to show the directories for library files. This time, add the folder for the SDL libraries. When you have followed this guide, that would be <tt>C:\Development\SDL-1.2.13\lib</tt>.

After you have done this, click OK to accept and close the options.

 
== Set up the solution ==
=== Conversion wizard ===
[[Image:Vce_guide2.png|thumb|Conversion wizard]]
Open the solution provided by DOSBox. It can be found as <tt>C:\Development\dosbox\visualc_net\dosbox.sln</tt>. If you have file extensions hidden (as they are by default), you may select "Solution files (*.sln)" from the object type dropdown to ensure you get the correct one. The first time you open the solution, VCE will present you with the Visual Studio Conversion Wizard, because the solution included in the DOSBox distribution is for an older version of Visual C++. You can simply click Finish and be done with it. If you want, you can take a look at the conversion log, but the information in there is not particularly interesting.
 
=== Dependencies ===
[[Image:Vce_guide3.png|thumb|Editing the additional dependencies]]
Now that the solution has been opened, it is necessary to disable some of the optional features of DOSBox. From the "Project" menu select "dosbox Properties". Expand the "Configuration Properties" and then the "Linker" category. Then choose "Input". From the properties on the right, you will need to remove some of the "Additional Dependencies". With the setup I have described here, I need to remove '''sdl_net.lib''', '''zlib.lib''', '''libpng.lib''' and '''curses.lib''' (you will also not need the odbc32.lib and odbccp32.lib references, but there is no harm in leaving them). Apply the changes and use the dropdown at the top left to switch to the Release configuration. Repeat the previous step, removing those same references and again apply the changes.
 
=== Configuration setup ===
[[Image:Vce_guide4.png|thumb|Adjusting the config.h file]]
In the Solution Explorer, browse down the solution into "Source files" and then "visualc". Open the file <tt>config.h</tt> listed there and do some editing. Find the line that reads
#define C_SSHOT 1
and change the 1 to a 0. Do the same for the lines mentioning <tt>C_MODEM</tt> and <tt>C_IPX</tt>. The reason we are disabling these options is that they require some extra libraries that we haven’t set up for this tutorial. Also, set <tt>C_CORE_INLINE</tt> to 1 to enable faster CPU emulation.

In the Solution Explorer, in the "Source files", you will find the file <tt>winres.rc</tt>. Right-click on that and choose "View code". ''Remove'' the line at the top that reads
#include "afxres.h"
When you have done this, save the solution ("Save all" from the file menu). This ensures you won’t have to repeat any of the previous steps.
 

== The actual build ==
[[Image:Vce_guide5.png|thumb|Build successfully completed]]
Before building, right click on "Solution 'dosbox'" in the Solution Explorer and go to Properties -> Configuration Properties. Set the Configuration dropdown box to "Release" instead of "Debug". This will cause VC++ to build an optimized binary without extra debug features.

Now that all this is done, press F7 to start the build process. There will be a few warnings, but they are unimportant. The build may take a few minutes depending on the speed of your computer, but if you have followed this tutorial it will complete successfully.

Note that to actually run the executable you have built, you will need the SDL library (<tt>SDL.DLL</tt>) from your regular DOSBox install and place it in the <tt>C:\Development\dosbox\visualc_net</tt> directory.

Building DOSBox with Visual Studio

2018-07-13T21:56:01Z

Rainwarrior: guide to getting and preparing libraries...

Building DOSBox with MinGW

2018-07-13T21:26:00Z

Rainwarrior: maybe give a tip about INSTALL too

Building DOSBox with MinGW

2018-07-13T21:11:37Z

Rainwarrior: linking guide by DosFreak in case it's helpful

DOSBox is a complicated project. This document aims to provide a step by step description of how to use the MinGW developement environment to successfully build DOSBox. An alternative is to use [[Building DOSBox with Visual Studio|Microsoft Visual Studio]].

This page will guide you through setting up MinGW to compile a current (SVN/CVS) version of DOSBox. Because of updates to compilers and libraries, this guide will not work with the 0.74 (the last official release, which is currently over 6 years old) source files.

An alternative guide is also available on the forums: https://www.vogons.org/viewtopic.php?f=31&t=55706

== Installing MinGW ==
* Download mingw-get-setup.exe from http://sourceforge.net/projects/mingw/
* Run the installer, choosing the defaults
* Once the '''MinGW Installation Manager''' application starts, select
** mingw-developer-toolkit (msys-base should be automatically added)
** mingw32-base
** mingw32-gcc-g++
* On the installation menu, apply changes, and confirm that you want to apply the changes

The installation manager is going to download a bunch of files, and at the end, start installing them. Once this is done, you can close the dialog box as well as the installation manager.

Well done, MinGW is now installed! Let's start it up.

* Browse to '''C:\MinGW\msys\1.0'''
* Run '''MSYS.BAT'''

This will start up a DOS prompt like screen, lets mount the base path
mount 'c:\MinGW' /mingw

You have now completed this section, lets move on to adding the SDL libraries to MinGW.

== Adding the SDL libraries to MinGW ==
* Download the pre compiled SDL development libraries from here http://www.libsdl.org/release/SDL-devel-1.2.15-mingw32.tar.gz
* Copy the downloaded file to your MSYS home folder, it's going to be something like '''C:\MinGW\msys\1.0\home\Administrator'''
* Switch back to the MSYS command prompt we started earlier
* Lets extract the downloaded files
tar xvf SDL-devel-1.2.15-mingw32.tar.gz
* And now add the files to MinGW
cd SDL-1.2.15
make install-sdl prefix=/mingw
cd ..

Cool, the SDL libraries have been added to MinGW, onto the next section.

== Adding Direct Draw support to DOSBox (Optional) ==
If you want to give DOSBox the option to use the DDRAW output option, then we need to add a couple of extra libraries to MinGW
* Download the following file, http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the files (the -C parameter, tells tar where to extract the files to)
tar xvf directx-devel.tar.gz -C /mingw

== Adding networking support to DOSBox (Optional) ==
These steps show you how to add the SDL_net libraries to MinGW, which enable networking and modem for DOSBox. If you aren't going to be using DOSBox for multi player games, then you can probably skip this step.
* Download the SDL_net source files from https://www.libsdl.org/projects/SDL_net/release/SDL_net-1.2.8.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_net-1.2.8.tar.gz
* Lets configure the libraries
cd SDL_net-1.2.8
./configure --prefix=/mingw
* '''SDLnet.c''' will have to be modified slightly to compile. Open it with a text editor and add the following #include near the top of the file:
#include <winerror.h>
* And now compile them
make
* And then install them (copy the files)
make install
cd ..

== Adding screenshot support (Optional) ==
This one is a bit tricky because it relies on two libraries, zlib (libpng needs these libraries), and libpng. We are also going to be compiling the libraries statically to keep external DLL's to a minimum.
* Download zlib from here http://sourceforge.net/projects/libpng/files/zlib/1.2.8/zlib-1.2.8.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf zlib-1.2.8.tar.xz
* Lets build the static library
cd zlib-1.2.8
make -f win32/Makefile.gcc
* And now copy the files to /mingw
cp libz.a /mingw/lib/
cp zlib.h zconf.h /mingw/include/
cd ..
Cool, that wasn't too hard, onto libpng
* Download libpng from here https://sourceforge.net/projects/libpng/files/libpng16/older-releases/1.6.18/libpng-1.6.18.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libpng-1.6.18.tar.xz
* Configure the library
cd libpng-1.6.18
./configure --disable-shared --prefix=/mingw
* There is currently [https://sourceforge.net/p/libpng/bugs/273/ a problem with the configure script] that will need to be manually resolved. Open '''pnglibconf.h''' with a text editor, and you will find several #define lines near the bottom that have been erroneously split into two lines. This can be fixed by adding a backslash to the end of the affected lines:
199: #define PNG_TEXT_Z_DEFAULT_COMPRESSION \
201: #define PNG_TEXT_Z_DEFAULT_STRATEGY \
209: #define PNG_ZLIB_VERNUM \
211: #define PNG_Z_DEFAULT_COMPRESSION \
213: #define PNG_Z_DEFAULT_NOFILTER_STRATEGY \
215: #define PNG_Z_DEFAULT_STRATEGY \
* And now to compile and install the files
make
make install
cd ..

== Adding support for compressed audio on diskimages (Optional) ==
This is for cue/bin cdrom images with compressed (ogg) audio tracks. We will be adding the libvorbis, libogg, and sdl_sound libraries.
* Download libogg from here http://downloads.xiph.org/releases/ogg/libogg-1.3.2.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libogg-1.3.2.tar.gz
* Configure the library, disabling shared library files
cd libogg-1.3.2
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download libvorbis from here http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.5.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libvorbis-1.3.5.tar.gz
* Configure the library, disabling shared library files
cd libvorbis-1.3.5
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download sdl_sound from here https://www.icculus.org/SDL_sound/downloads/SDL_sound-1.0.3.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_sound-1.0.3.tar.gz
* Configure and compile
cd SDL_sound-1.0.3
./configure --disable-shared --prefix=/mingw LIBS="-lvorbisfile -lvorbis -logg"
make
make install
cd ..

== Enabling the debugger (You probably don't want this) ==
The debugger is mainly for developers of DOSBox, so they can find out why a game isn't working.
* Download the PDCurses source files from http://sourceforge.net/projects/pdcurses/files/pdcurses/3.4/PDCurses-3.4.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf PDCurses-3.4.tar.gz
* Compile the library
cd PDCurses-3.4/win32
make -f gccwin32.mak DLL=N
* And now copy the files to your /mingw folders
cp pdcurses.a /mingw/lib/libpdcurses.a
cd ..
cp curses.h panel.h /mingw/include/
cd ..

== Compiling DOSBox ==
* If you plan on rebuilding periodically with the latest code, you can check out the Subversion repository here: https://sourceforge.net/p/dosbox/code-0/HEAD/tree/dosbox/trunk/
* Otherwise you can download a snapshot of the latest DOSBox SVN source here: http://source.dosbox.com/dosboxsvn.tgz
* See also [[SVN Builds]] for a list of unofficial alternative versions of DOSBox that you may wish to try instead. Many of them have additional features.

* If using the snapshot, copy that file to your MSYS home folder, and extract the file
tar xvf dosboxsvn.tgz
* Let's configure DOSBox, and tell it to use the static C library (-static-libgcc) and C++ library (-static-libstdc++) and stripping the final EXE of debug information (-s)
cd dosbox
./autogen.sh
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s"
* For SDL_sound support, you have to extra some extra parameters so that the configure command knows where to find the audio library files (LIBS="-lvorbisfile.....)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg"
* If you want to enable debugging (you probably don't)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg" --enable-debug
* And now for compiling DOSBox
make
* The last step is to gather all the files together in a folder
** Create a folder with a name of your choosing
** Copy the dosbox.exe file located under the '''dosbox\src''' folder, e.g. '''C:\MinGW\msys\1.0\home\Administrator\dosbox\src''' to the folder you created
** Copy the SDL.dll file located under '''SDL-1.2.15\bin''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL-1.2.15\bin''' to the folder you created
** Optionally, copy the SDL_net.dll file located under '''SDL_net-1.2.8\.libs''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL_net-1.2.8\.libs''' to the folder you created

Start up DOSBox, and see if it works.

Building DOSBox with Visual Studio

2018-07-13T21:01:23Z

Rainwarrior: updating lead and information about getting Visual Studio

SVN Builds

2018-07-13T20:44:15Z

Rainwarrior: link to sourceforge page probably belongs in lead

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.

The official DOSBox SVN repository is hosted at sourceforge.net:
: https://sourceforge.net/projects/dosbox/

==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 [http://www.sourceforge.net/ sourceforge.net] 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. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release (0.74) is several years old, and is therefore missing a significant amount of work performed by the developers. 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 [http://www.vogons.org/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 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 [http://www.vogons.org/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? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 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:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.12 (ppc/intel)
** URL: https://www.dropbox.com/s/kbrf5elbcu66kst/Dosbox-Snapshot.dmg?dl=1
** Notes: Automatically updated on changes to SVN.

===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 SVN-lfn''' (DOSBox with Long File Name (LFN), mouse copy/paste support and more) by Wengier
** Last updated: 2017-09-20
** SVN base version: r4052
** URL: http://www.wpdos.org/dosbox-vdos-lfn.html (introduction + source + Windows binary + links to forum discussions)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** URL: http://bit.ly/1laDvGX (alternative Windows binary compiled with MinGW instead of Visual Studio, zipped)
** Description: This is an enhanced build of DOSBox based on its SVN version that adds features like Windows-style Long File Name (LFN) and mouse copy/paste support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). It now also includes features such as automatic drive mounting, improved command-line handling, APM power off, direct parallel port passthrough used for printing, DOS APIs that communicate with the Windows clipboard, and DBCS support for displaying CJK (East Asian) characters. Windows binaries are provided, but sources should work on other platforms such as Linux and macOS/OS X too (pdcurses might be required for the cross-platform clipboard copy/paste feature). Please see README.TXT file inside the binary package for more information.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The last version broke this build in various places and uses out of date and not fully working changes of the DOSBox-X branch. It is no longer recommended to use it.The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** 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: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** 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 sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/4052/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2017-09-20'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===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:
* [[BuildingDOSBox]]

===Unofficial ports===
The following DOSBoxWiki article discusses unofficial ports for other operating systems, which are not in any way supported by the DOSBox team.
* [[Unofficial ports]]

===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) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* https://sourceforge.net/p/dosbox/code-0/HEAD/tree/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

SVN Builds

2018-07-13T20:42:40Z

Rainwarrior: /* Snapshot of latest DOSBox SVN source code */ updating links, removing links that don't work

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 [http://www.sourceforge.net/ sourceforge.net] 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. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release (0.74) is several years old, and is therefore missing a significant amount of work performed by the developers. 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 [http://www.vogons.org/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 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 [http://www.vogons.org/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? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://www.vogons.org/viewtopic.php?t=9306 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:

* '''EmuCR''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.12 (ppc/intel)
** URL: https://www.dropbox.com/s/kbrf5elbcu66kst/Dosbox-Snapshot.dmg?dl=1
** Notes: Automatically updated on changes to SVN.

===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 SVN-lfn''' (DOSBox with Long File Name (LFN), mouse copy/paste support and more) by Wengier
** Last updated: 2017-09-20
** SVN base version: r4052
** URL: http://www.wpdos.org/dosbox-vdos-lfn.html (introduction + source + Windows binary + links to forum discussions)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** URL: http://bit.ly/1laDvGX (alternative Windows binary compiled with MinGW instead of Visual Studio, zipped)
** Description: This is an enhanced build of DOSBox based on its SVN version that adds features like Windows-style Long File Name (LFN) and mouse copy/paste support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). It now also includes features such as automatic drive mounting, improved command-line handling, APM power off, direct parallel port passthrough used for printing, DOS APIs that communicate with the Windows clipboard, and DBCS support for displaying CJK (East Asian) characters. Windows binaries are provided, but sources should work on other platforms such as Linux and macOS/OS X too (pdcurses might be required for the cross-platform clipboard copy/paste feature). Please see README.TXT file inside the binary package for more information.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

===Obsolete SVN/CVS builds===
These builds appear to be no longer maintained, and are listed here for historical reference.

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** URL: http://cafe.daum.net/dosbox
** Description: The last version broke this build in various places and uses out of date and not fully working changes of the DOSBox-X branch. It is no longer recommended to use it.The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc. Recent versions include DOSBox-X branch changes as well.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''Tharos (by XTale)'''
** Last updated: 2010-03-28
** <s>URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc</s>
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

* '''gulikoza'''
** Last Updated: 2009-07-09
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** 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: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** 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 sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://sourceforge.net/p/dosbox/code-0/4052/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2017-09-20'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://www.vogons.org/viewtopic.php?t=7323

===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:
* [[BuildingDOSBox]]

===Unofficial ports===
The following DOSBoxWiki article discusses unofficial ports for other operating systems, which are not in any way supported by the DOSBox team.
* [[Unofficial ports]]

===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) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* https://sourceforge.net/p/dosbox/code-0/HEAD/tree/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)

Building DOSBox with MinGW

2018-07-13T20:34:38Z

Rainwarrior: mv Visual C 2008 Express to Visual Studio

DOSBox is a complicated project. This document aims to provide a step by step description of how to use the MinGW developement environment to successfully build DOSBox. An alternative is to use [[Building DOSBox with Visual Studio|Microsoft Visual Studio]].

This page will guide you through setting up MinGW to compile a current (SVN/CVS) version of DOSBox. Because of updates to compilers and libraries, this guide will not work with the 0.74 (the last official release, which is currently over 6 years old) source files.

== Installing MinGW ==
* Download mingw-get-setup.exe from http://sourceforge.net/projects/mingw/
* Run the installer, choosing the defaults
* Once the '''MinGW Installation Manager''' application starts, select
** mingw-developer-toolkit (msys-base should be automatically added)
** mingw32-base
** mingw32-gcc-g++
* On the installation menu, apply changes, and confirm that you want to apply the changes

The installation manager is going to download a bunch of files, and at the end, start installing them. Once this is done, you can close the dialog box as well as the installation manager.

Well done, MinGW is now installed! Let's start it up.

* Browse to '''C:\MinGW\msys\1.0'''
* Run '''MSYS.BAT'''

This will start up a DOS prompt like screen, lets mount the base path
mount 'c:\MinGW' /mingw

You have now completed this section, lets move on to adding the SDL libraries to MinGW.

== Adding the SDL libraries to MinGW ==
* Download the pre compiled SDL development libraries from here http://www.libsdl.org/release/SDL-devel-1.2.15-mingw32.tar.gz
* Copy the downloaded file to your MSYS home folder, it's going to be something like '''C:\MinGW\msys\1.0\home\Administrator'''
* Switch back to the MSYS command prompt we started earlier
* Lets extract the downloaded files
tar xvf SDL-devel-1.2.15-mingw32.tar.gz
* And now add the files to MinGW
cd SDL-1.2.15
make install-sdl prefix=/mingw
cd ..

Cool, the SDL libraries have been added to MinGW, onto the next section.

== Adding Direct Draw support to DOSBox (Optional) ==
If you want to give DOSBox the option to use the DDRAW output option, then we need to add a couple of extra libraries to MinGW
* Download the following file, http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the files (the -C parameter, tells tar where to extract the files to)
tar xvf directx-devel.tar.gz -C /mingw

== Adding networking support to DOSBox (Optional) ==
These steps show you how to add the SDL_net libraries to MinGW, which enable networking and modem for DOSBox. If you aren't going to be using DOSBox for multi player games, then you can probably skip this step.
* Download the SDL_net source files from https://www.libsdl.org/projects/SDL_net/release/SDL_net-1.2.8.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_net-1.2.8.tar.gz
* Lets configure the libraries
cd SDL_net-1.2.8
./configure --prefix=/mingw
* '''SDLnet.c''' will have to be modified slightly to compile. Open it with a text editor and add the following #include near the top of the file:
#include <winerror.h>
* And now compile them
make
* And then install them (copy the files)
make install
cd ..

== Adding screenshot support (Optional) ==
This one is a bit tricky because it relies on two libraries, zlib (libpng needs these libraries), and libpng. We are also going to be compiling the libraries statically to keep external DLL's to a minimum.
* Download zlib from here http://sourceforge.net/projects/libpng/files/zlib/1.2.8/zlib-1.2.8.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf zlib-1.2.8.tar.xz
* Lets build the static library
cd zlib-1.2.8
make -f win32/Makefile.gcc
* And now copy the files to /mingw
cp libz.a /mingw/lib/
cp zlib.h zconf.h /mingw/include/
cd ..
Cool, that wasn't too hard, onto libpng
* Download libpng from here https://sourceforge.net/projects/libpng/files/libpng16/older-releases/1.6.18/libpng-1.6.18.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libpng-1.6.18.tar.xz
* Configure the library
cd libpng-1.6.18
./configure --disable-shared --prefix=/mingw
* There is currently [https://sourceforge.net/p/libpng/bugs/273/ a problem with the configure script] that will need to be manually resolved. Open '''pnglibconf.h''' with a text editor, and you will find several #define lines near the bottom that have been erroneously split into two lines. This can be fixed by adding a backslash to the end of the affected lines:
199: #define PNG_TEXT_Z_DEFAULT_COMPRESSION \
201: #define PNG_TEXT_Z_DEFAULT_STRATEGY \
209: #define PNG_ZLIB_VERNUM \
211: #define PNG_Z_DEFAULT_COMPRESSION \
213: #define PNG_Z_DEFAULT_NOFILTER_STRATEGY \
215: #define PNG_Z_DEFAULT_STRATEGY \
* And now to compile and install the files
make
make install
cd ..

== Adding support for compressed audio on diskimages (Optional) ==
This is for cue/bin cdrom images with compressed (ogg) audio tracks. We will be adding the libvorbis, libogg, and sdl_sound libraries.
* Download libogg from here http://downloads.xiph.org/releases/ogg/libogg-1.3.2.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libogg-1.3.2.tar.gz
* Configure the library, disabling shared library files
cd libogg-1.3.2
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download libvorbis from here http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.5.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libvorbis-1.3.5.tar.gz
* Configure the library, disabling shared library files
cd libvorbis-1.3.5
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download sdl_sound from here https://www.icculus.org/SDL_sound/downloads/SDL_sound-1.0.3.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_sound-1.0.3.tar.gz
* Configure and compile
cd SDL_sound-1.0.3
./configure --disable-shared --prefix=/mingw LIBS="-lvorbisfile -lvorbis -logg"
make
make install
cd ..

== Enabling the debugger (You probably don't want this) ==
The debugger is mainly for developers of DOSBox, so they can find out why a game isn't working.
* Download the PDCurses source files from http://sourceforge.net/projects/pdcurses/files/pdcurses/3.4/PDCurses-3.4.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf PDCurses-3.4.tar.gz
* Compile the library
cd PDCurses-3.4/win32
make -f gccwin32.mak DLL=N
* And now copy the files to your /mingw folders
cp pdcurses.a /mingw/lib/libpdcurses.a
cd ..
cp curses.h panel.h /mingw/include/
cd ..

== Compiling DOSBox ==
* If you plan on rebuilding periodically with the latest code, you can check out the Subversion repository here: https://sourceforge.net/p/dosbox/code-0/HEAD/tree/dosbox/trunk/
* Otherwise you can download a snapshot of the latest DOSBox SVN source here: http://source.dosbox.com/dosboxsvn.tgz
* See also [[SVN Builds]] for a list of unofficial alternative versions of DOSBox that you may wish to try instead. Many of them have additional features.

* If using the snapshot, copy that file to your MSYS home folder, and extract the file
tar xvf dosboxsvn.tgz
* Let's configure DOSBox, and tell it to use the static C library (-static-libgcc) and C++ library (-static-libstdc++) and stripping the final EXE of debug information (-s)
cd dosbox
./autogen.sh
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s"
* For SDL_sound support, you have to extra some extra parameters so that the configure command knows where to find the audio library files (LIBS="-lvorbisfile.....)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg"
* If you want to enable debugging (you probably don't)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg" --enable-debug
* And now for compiling DOSBox
make
* The last step is to gather all the files together in a folder
** Create a folder with a name of your choosing
** Copy the dosbox.exe file located under the '''dosbox\src''' folder, e.g. '''C:\MinGW\msys\1.0\home\Administrator\dosbox\src''' to the folder you created
** Copy the SDL.dll file located under '''SDL-1.2.15\bin''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL-1.2.15\bin''' to the folder you created
** Optionally, copy the SDL_net.dll file located under '''SDL_net-1.2.8\.libs''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL_net-1.2.8\.libs''' to the folder you created

Start up DOSBox, and see if it works.

BuildingDOSBox

2018-07-13T20:33:55Z

Rainwarrior: mv Visual C 2008 Express to Visual Studio

You can build your own copy of DOSBox under Windows using either MinGW or Microsoft Visual Studio.

For more information on building DOSBox please see:
*[[Building DOSBox with MinGW]]
*[[Building DOSBox with Visual Studio]]

See also [[SVN Builds]] for plain and enhanced SVN builds and [[unofficial ports]] for other ports.

Main Page

2018-07-13T20:31:14Z

Rainwarrior: /* Advanced Topics */ mv Visual C 2008 Express to Visual Studio

'''
=Welcome to the Wiki page of the DOSBox project=

'''DOSBox''' emulates an Intel x86 PC, complete with [[Sound|sound]], [[Display|graphics]], [[Input|mouse]], [[Input|joystick]], [[Connectivity|modem]], etc., necessary for running many old MS-DOS [[GAMES|games]] that simply cannot be run on modern PCs and operating systems, such as Microsoft Windows XP, Windows Vista, Linux and FreeBSD. However, it is not restricted to running only games. In theory, any MS-DOS or PC-DOS (referred to commonly as "DOS") [[Software|application]] should run in DOSBox, but the emphasis has been on getting DOS [[GAMES|games]] to run smoothly, which means that communication, networking and printer support are still in early development.

DOSBox also comes with its own [[Command Line|DOS-like command prompt]]. It is still quite rudimentary and lacks many of the features found in MS-DOS, but it is sufficient for installing and running most DOS [[GAMES|games]].

DOSBox has a lively, user-supported [http://www.vogons.org/viewforum.php?f=53 community forum] hosted at VOGONS (Very Old Games On New Systems). Feel very very free to drop by if you have questions about DOSBox!

==General Information==
*[[Releases]] - Download DOSBox
*[[System Requirements]]
*[[DOSBox_FAQ|Frequently Asked Questions]] (FAQ)
*Guides
**[[Basic_Setup_and_Installation_of_DosBox|Basic Setup and Installation of DOSBox]]
***[[DOSBox and Windows Vista|Vista Specific Issues]]
***[[DOSBox and Mac OSX|Mac OSX Specific Issues]]
***[[Mac OSX Advanced]]
***[[Recording Video]]
**[[Contributing to this Wiki]]
**[[GAMES|Games]] that DOSBox can (or can't) run
**[[Software]] applications that DOSBox can (or can't) run
**[[TOOLS|Tools]] that can assist either playing games or using DOSBox generally
**[[DOSBoxFrontends|Frontends]] - simplifies running and understanding DOSBox.
**[[Performance|Running Resource Demanding Games]]
*[[Special Thanks]]
*[[Contact]]

==More Specific Topics==
*[[Usage| DOSBox.exe Supported Parameters]]
*[[ZDrive|Z:\> Prompt]]
*[[Commands|Command Line Utilities]]
**[[MOUNT|Mounting your CD-ROM in DOSBox]]
*[[Special Keys]]
*[[dosbox.conf|The Configuration File]] (dosbox.conf)
**[[Associating the Configuration File in Windows]]
*[[Language File|The Language File]]
*[[Keymapper|The Keymapper]]
*[[Ubuntu Configuration|Ubuntu Configuration]]
*[[Network_Setup|Network Setup]] (SerialPPP, SLIP and IPX-tunneling)
*[[DOSBoxShortcuts|DOSBox Shortcuts]]
*[[GOG_games_that_use_DOSBox|GOG Games that use DOSBox]] - An overview

==DOSBox resources==
*[[SVN Builds|DOSBox SVN Builds]] - Plain and enhanced SVN builds of DOSBox
*[[Unofficial ports]] - DOSBox for other operating systems and hardware platforms (unsupported)
*[http://dosbox.cvs.sourceforge.net/dosbox/dosbox/README?view=markup DOSBox README File]
*[http://dosbox.com/comp_list.php List of Games and Applications] (and how to install and run them)
*[http://www.vogons.org/viewforum.php?f=53 DOSBox community forum]


==Advanced Topics==
*[[BuildingDOSBox]] - Building your own version of DOSBox
**[[Building DOSBox with MinGW]]
**[[Building DOSBox with Visual Studio]]
*[https://wiki.libsdl.org/FAQUsingSDL Using SDL FAQ] (SDL environment variables that can make or break things)
*[[Special:Allpages|Index of all articles]]

Building DOSBox with Visual C 2008 Express

2018-07-13T20:29:53Z

Rainwarrior: Rainwarrior moved page Building DOSBox with Visual C 2008 Express to Building DOSBox with Visual Studio: giving this page a new title that isn't permanently fixed in time

#REDIRECT [[Building DOSBox with Visual Studio]]

Building DOSBox with Visual Studio

2018-07-13T20:29:53Z

Rainwarrior: Rainwarrior moved page Building DOSBox with Visual C 2008 Express to Building DOSBox with Visual Studio: giving this page a new title that isn't permanently fixed in time

{{DISPLAYTITLE:Building DOSBox with Visual C++ 2008 Express}}
Note: The title of this page should actually be "''Building DOSBox with Visual C++ 2008 Express''", but the Wiki software does not allow the use of the + character in a title.

DOSBox is a complicated project. This document aims to provide a step by step description of how to use the free Express Edition of Microsoft's Visual C++ 2008 to successfully build DOSBox. An alternative is to use [[Building DOSBox with MinGW|MinGW]].

== Get Visual C++ 2008 Express ==
Microsoft provides the Express edition of Visual C++ 2008 for free. Download VCE [http://www.microsoft.com/Express/vc/ directly from Microsoft] and install it. When installing, you don’t need to select any of the optional components like the Silverlight runtime, SQL Server or the MSDN Express Library. After the installation is complete, you will need to restart your computer.

== Get the SDL library ==
To be able to build DOSBox, you will also need the development libraries for SDL. At the time of writing, the most current release of SDL is 1.2.13. From the downloads section at the [http://www.libsdl.org/ SDL website] look for the Development Libraries for Win32, marked for Visual C++ 2005 Service Pack 1. The filename will be something like <tt>SDL-devel-1.2.13-VC8.zip</tt>. Unpack this file to the location of your choosing. For this discussion, I shall place it in <tt>C:\Development\SDL-1.2.13</tt>.

== Get the DOSBox sources ==
The next step is to get DOSBox itself. At the time of writing, the latest official release of DOSBox is 0.74, available at the [[Releases]] page. However, it was released over 6 years ago, so if you want more recent source code you can go to the [[SVN Builds]] page to download the source of some SVN version of DOSBox. Since the DOSBox sources come as a <tt>.tar.gz</tt> file, you may need a separate program to extract this. Unpack the source to the location of your choosing. For this discussion, I have chosen <tt>C:\Development\dosbox</tt>.

== Set up the environment ==
[[Image:Vce_guide1.png|thumb|Setting the include directories for SDL]]
From your start menu, start VCE. After a few moments, the IDE (Integrated Development Environment) will start. The first thing we need to do is tell VCE where to find SDL. From the "Tools" menu select "Options". When the Options menu appears, expand the category "Projects and Solutions" and choose "VC++ Directories". From the directories pulldown, choose to show the directories for include files, click the folder icon and add the folder for the SDL includes. If you have been following this guide literally, that would <tt>C:\Development\SDL-1.2.13\include</tt>. Next, elect to show the directories for library files. This time, add the folder for the SDL libraries. When you have followed this guide, that would be <tt>C:\Development\SDL-1.2.13\lib</tt>.

After you have done this, click OK to accept and close the options.

 
== Set up the solution ==
=== Conversion wizard ===
[[Image:Vce_guide2.png|thumb|Conversion wizard]]
Open the solution provided by DOSBox. It can be found as <tt>C:\Development\dosbox\visualc_net\dosbox.sln</tt>. If you have file extensions hidden (as they are by default), you may select "Solution files (*.sln)" from the object type dropdown to ensure you get the correct one. The first time you open the solution, VCE will present you with the Visual Studio Conversion Wizard, because the solution included in the DOSBox distribution is for an older version of Visual C++. You can simply click Finish and be done with it. If you want, you can take a look at the conversion log, but the information in there is not particularly interesting.
 
=== Dependencies ===
[[Image:Vce_guide3.png|thumb|Editing the additional dependencies]]
Now that the solution has been opened, it is necessary to disable some of the optional features of DOSBox. From the "Project" menu select "dosbox Properties". Expand the "Configuration Properties" and then the "Linker" category. Then choose "Input". From the properties on the right, you will need to remove some of the "Additional Dependencies". With the setup I have described here, I need to remove '''sdl_net.lib''', '''zlib.lib''', '''libpng.lib''' and '''curses.lib''' (you will also not need the odbc32.lib and odbccp32.lib references, but there is no harm in leaving them). Apply the changes and use the dropdown at the top left to switch to the Release configuration. Repeat the previous step, removing those same references and again apply the changes.
 
=== Configuration setup ===
[[Image:Vce_guide4.png|thumb|Adjusting the config.h file]]
In the Solution Explorer, browse down the solution into "Source files" and then "visualc". Open the file <tt>config.h</tt> listed there and do some editing. Find the line that reads
#define C_SSHOT 1
and change the 1 to a 0. Do the same for the lines mentioning <tt>C_MODEM</tt> and <tt>C_IPX</tt>. The reason we are disabling these options is that they require some extra libraries that we haven’t set up for this tutorial. Also, set <tt>C_CORE_INLINE</tt> to 1 to enable faster CPU emulation.

In the Solution Explorer, in the "Source files", you will find the file <tt>winres.rc</tt>. Right-click on that and choose "View code". ''Remove'' the line at the top that reads
#include "afxres.h"
When you have done this, save the solution ("Save all" from the file menu). This ensures you won’t have to repeat any of the previous steps.
 

== The actual build ==
[[Image:Vce_guide5.png|thumb|Build successfully completed]]
Before building, right click on "Solution 'dosbox'" in the Solution Explorer and go to Properties -> Configuration Properties. Set the Configuration dropdown box to "Release" instead of "Debug". This will cause VC++ to build an optimized binary without extra debug features.

Now that all this is done, press F7 to start the build process. There will be a few warnings, but they are unimportant. The build may take a few minutes depending on the speed of your computer, but if you have followed this tutorial it will complete successfully.

Note that to actually run the executable you have built, you will need the SDL library (<tt>SDL.DLL</tt>) from your regular DOSBox install and place it in the <tt>C:\Development\dosbox\visualc_net</tt> directory.

Building DOSBox with MinGW

2018-07-13T20:17:16Z

Rainwarrior: /* Compiling DOSBox */ adding suggestion that you might want a SVN checkout instead of just the snapshot

DOSBox is a complicated project. This document aims to provide a step by step description of how to use the MinGW developement environment to successfully build DOSBox. An alternative is to use [[Building DOSBox with Visual C 2008 Express|Microsoft Visual Studio]].

This page will guide you through setting up MinGW to compile a current (SVN/CVS) version of DOSBox. Because of updates to compilers and libraries, this guide will not work with the 0.74 (the last official release, which is currently over 6 years old) source files.

== Installing MinGW ==
* Download mingw-get-setup.exe from http://sourceforge.net/projects/mingw/
* Run the installer, choosing the defaults
* Once the '''MinGW Installation Manager''' application starts, select
** mingw-developer-toolkit (msys-base should be automatically added)
** mingw32-base
** mingw32-gcc-g++
* On the installation menu, apply changes, and confirm that you want to apply the changes

The installation manager is going to download a bunch of files, and at the end, start installing them. Once this is done, you can close the dialog box as well as the installation manager.

Well done, MinGW is now installed! Let's start it up.

* Browse to '''C:\MinGW\msys\1.0'''
* Run '''MSYS.BAT'''

This will start up a DOS prompt like screen, lets mount the base path
mount 'c:\MinGW' /mingw

You have now completed this section, lets move on to adding the SDL libraries to MinGW.

== Adding the SDL libraries to MinGW ==
* Download the pre compiled SDL development libraries from here http://www.libsdl.org/release/SDL-devel-1.2.15-mingw32.tar.gz
* Copy the downloaded file to your MSYS home folder, it's going to be something like '''C:\MinGW\msys\1.0\home\Administrator'''
* Switch back to the MSYS command prompt we started earlier
* Lets extract the downloaded files
tar xvf SDL-devel-1.2.15-mingw32.tar.gz
* And now add the files to MinGW
cd SDL-1.2.15
make install-sdl prefix=/mingw
cd ..

Cool, the SDL libraries have been added to MinGW, onto the next section.

== Adding Direct Draw support to DOSBox (Optional) ==
If you want to give DOSBox the option to use the DDRAW output option, then we need to add a couple of extra libraries to MinGW
* Download the following file, http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the files (the -C parameter, tells tar where to extract the files to)
tar xvf directx-devel.tar.gz -C /mingw

== Adding networking support to DOSBox (Optional) ==
These steps show you how to add the SDL_net libraries to MinGW, which enable networking and modem for DOSBox. If you aren't going to be using DOSBox for multi player games, then you can probably skip this step.
* Download the SDL_net source files from https://www.libsdl.org/projects/SDL_net/release/SDL_net-1.2.8.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_net-1.2.8.tar.gz
* Lets configure the libraries
cd SDL_net-1.2.8
./configure --prefix=/mingw
* '''SDLnet.c''' will have to be modified slightly to compile. Open it with a text editor and add the following #include near the top of the file:
#include <winerror.h>
* And now compile them
make
* And then install them (copy the files)
make install
cd ..

== Adding screenshot support (Optional) ==
This one is a bit tricky because it relies on two libraries, zlib (libpng needs these libraries), and libpng. We are also going to be compiling the libraries statically to keep external DLL's to a minimum.
* Download zlib from here http://sourceforge.net/projects/libpng/files/zlib/1.2.8/zlib-1.2.8.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf zlib-1.2.8.tar.xz
* Lets build the static library
cd zlib-1.2.8
make -f win32/Makefile.gcc
* And now copy the files to /mingw
cp libz.a /mingw/lib/
cp zlib.h zconf.h /mingw/include/
cd ..
Cool, that wasn't too hard, onto libpng
* Download libpng from here https://sourceforge.net/projects/libpng/files/libpng16/older-releases/1.6.18/libpng-1.6.18.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libpng-1.6.18.tar.xz
* Configure the library
cd libpng-1.6.18
./configure --disable-shared --prefix=/mingw
* There is currently [https://sourceforge.net/p/libpng/bugs/273/ a problem with the configure script] that will need to be manually resolved. Open '''pnglibconf.h''' with a text editor, and you will find several #define lines near the bottom that have been erroneously split into two lines. This can be fixed by adding a backslash to the end of the affected lines:
199: #define PNG_TEXT_Z_DEFAULT_COMPRESSION \
201: #define PNG_TEXT_Z_DEFAULT_STRATEGY \
209: #define PNG_ZLIB_VERNUM \
211: #define PNG_Z_DEFAULT_COMPRESSION \
213: #define PNG_Z_DEFAULT_NOFILTER_STRATEGY \
215: #define PNG_Z_DEFAULT_STRATEGY \
* And now to compile and install the files
make
make install
cd ..

== Adding support for compressed audio on diskimages (Optional) ==
This is for cue/bin cdrom images with compressed (ogg) audio tracks. We will be adding the libvorbis, libogg, and sdl_sound libraries.
* Download libogg from here http://downloads.xiph.org/releases/ogg/libogg-1.3.2.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libogg-1.3.2.tar.gz
* Configure the library, disabling shared library files
cd libogg-1.3.2
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download libvorbis from here http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.5.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libvorbis-1.3.5.tar.gz
* Configure the library, disabling shared library files
cd libvorbis-1.3.5
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download sdl_sound from here https://www.icculus.org/SDL_sound/downloads/SDL_sound-1.0.3.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_sound-1.0.3.tar.gz
* Configure and compile
cd SDL_sound-1.0.3
./configure --disable-shared --prefix=/mingw LIBS="-lvorbisfile -lvorbis -logg"
make
make install
cd ..

== Enabling the debugger (You probably don't want this) ==
The debugger is mainly for developers of DOSBox, so they can find out why a game isn't working.
* Download the PDCurses source files from http://sourceforge.net/projects/pdcurses/files/pdcurses/3.4/PDCurses-3.4.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf PDCurses-3.4.tar.gz
* Compile the library
cd PDCurses-3.4/win32
make -f gccwin32.mak DLL=N
* And now copy the files to your /mingw folders
cp pdcurses.a /mingw/lib/libpdcurses.a
cd ..
cp curses.h panel.h /mingw/include/
cd ..

== Compiling DOSBox ==
* If you plan on rebuilding periodically with the latest code, you can check out the Subversion repository here: https://sourceforge.net/p/dosbox/code-0/HEAD/tree/dosbox/trunk/
* Otherwise you can download a snapshot of the latest DOSBox SVN source here: http://source.dosbox.com/dosboxsvn.tgz
* See also [[SVN Builds]] for a list of unofficial alternative versions of DOSBox that you may wish to try instead. Many of them have additional features.

* If using the snapshot, copy that file to your MSYS home folder, and extract the file
tar xvf dosboxsvn.tgz
* Let's configure DOSBox, and tell it to use the static C library (-static-libgcc) and C++ library (-static-libstdc++) and stripping the final EXE of debug information (-s)
cd dosbox
./autogen.sh
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s"
* For SDL_sound support, you have to extra some extra parameters so that the configure command knows where to find the audio library files (LIBS="-lvorbisfile.....)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg"
* If you want to enable debugging (you probably don't)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg" --enable-debug
* And now for compiling DOSBox
make
* The last step is to gather all the files together in a folder
** Create a folder with a name of your choosing
** Copy the dosbox.exe file located under the '''dosbox\src''' folder, e.g. '''C:\MinGW\msys\1.0\home\Administrator\dosbox\src''' to the folder you created
** Copy the SDL.dll file located under '''SDL-1.2.15\bin''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL-1.2.15\bin''' to the folder you created
** Optionally, copy the SDL_net.dll file located under '''SDL_net-1.2.8\.libs''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL_net-1.2.8\.libs''' to the folder you created

Start up DOSBox, and see if it works.

Building DOSBox with MinGW

2018-07-13T19:52:36Z

Rainwarrior: /* Adding networking support to DOSBox (Optional) */ bold for SDLnet.c filename

DOSBox is a complicated project. This document aims to provide a step by step description of how to use the MinGW developement environment to successfully build DOSBox. An alternative is to use [[Building DOSBox with Visual C 2008 Express|Microsoft Visual Studio]].

This page will guide you through setting up MinGW to compile a current (SVN/CVS) version of DOSBox. Because of updates to compilers and libraries, this guide will not work with the 0.74 (the last official release, which is currently over 6 years old) source files.

== Installing MinGW ==
* Download mingw-get-setup.exe from http://sourceforge.net/projects/mingw/
* Run the installer, choosing the defaults
* Once the '''MinGW Installation Manager''' application starts, select
** mingw-developer-toolkit (msys-base should be automatically added)
** mingw32-base
** mingw32-gcc-g++
* On the installation menu, apply changes, and confirm that you want to apply the changes

The installation manager is going to download a bunch of files, and at the end, start installing them. Once this is done, you can close the dialog box as well as the installation manager.

Well done, MinGW is now installed! Let's start it up.

* Browse to '''C:\MinGW\msys\1.0'''
* Run '''MSYS.BAT'''

This will start up a DOS prompt like screen, lets mount the base path
mount 'c:\MinGW' /mingw

You have now completed this section, lets move on to adding the SDL libraries to MinGW.

== Adding the SDL libraries to MinGW ==
* Download the pre compiled SDL development libraries from here http://www.libsdl.org/release/SDL-devel-1.2.15-mingw32.tar.gz
* Copy the downloaded file to your MSYS home folder, it's going to be something like '''C:\MinGW\msys\1.0\home\Administrator'''
* Switch back to the MSYS command prompt we started earlier
* Lets extract the downloaded files
tar xvf SDL-devel-1.2.15-mingw32.tar.gz
* And now add the files to MinGW
cd SDL-1.2.15
make install-sdl prefix=/mingw
cd ..

Cool, the SDL libraries have been added to MinGW, onto the next section.

== Adding Direct Draw support to DOSBox (Optional) ==
If you want to give DOSBox the option to use the DDRAW output option, then we need to add a couple of extra libraries to MinGW
* Download the following file, http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the files (the -C parameter, tells tar where to extract the files to)
tar xvf directx-devel.tar.gz -C /mingw

== Adding networking support to DOSBox (Optional) ==
These steps show you how to add the SDL_net libraries to MinGW, which enable networking and modem for DOSBox. If you aren't going to be using DOSBox for multi player games, then you can probably skip this step.
* Download the SDL_net source files from https://www.libsdl.org/projects/SDL_net/release/SDL_net-1.2.8.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_net-1.2.8.tar.gz
* Lets configure the libraries
cd SDL_net-1.2.8
./configure --prefix=/mingw
* '''SDLnet.c''' will have to be modified slightly to compile. Open it with a text editor and add the following #include near the top of the file:
#include <winerror.h>
* And now compile them
make
* And then install them (copy the files)
make install
cd ..

== Adding screenshot support (Optional) ==
This one is a bit tricky because it relies on two libraries, zlib (libpng needs these libraries), and libpng. We are also going to be compiling the libraries statically to keep external DLL's to a minimum.
* Download zlib from here http://sourceforge.net/projects/libpng/files/zlib/1.2.8/zlib-1.2.8.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf zlib-1.2.8.tar.xz
* Lets build the static library
cd zlib-1.2.8
make -f win32/Makefile.gcc
* And now copy the files to /mingw
cp libz.a /mingw/lib/
cp zlib.h zconf.h /mingw/include/
cd ..
Cool, that wasn't too hard, onto libpng
* Download libpng from here https://sourceforge.net/projects/libpng/files/libpng16/older-releases/1.6.18/libpng-1.6.18.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libpng-1.6.18.tar.xz
* Configure the library
cd libpng-1.6.18
./configure --disable-shared --prefix=/mingw
* There is currently [https://sourceforge.net/p/libpng/bugs/273/ a problem with the configure script] that will need to be manually resolved. Open '''pnglibconf.h''' with a text editor, and you will find several #define lines near the bottom that have been erroneously split into two lines. This can be fixed by adding a backslash to the end of the affected lines:
199: #define PNG_TEXT_Z_DEFAULT_COMPRESSION \
201: #define PNG_TEXT_Z_DEFAULT_STRATEGY \
209: #define PNG_ZLIB_VERNUM \
211: #define PNG_Z_DEFAULT_COMPRESSION \
213: #define PNG_Z_DEFAULT_NOFILTER_STRATEGY \
215: #define PNG_Z_DEFAULT_STRATEGY \
* And now to compile and install the files
make
make install
cd ..

== Adding support for compressed audio on diskimages (Optional) ==
This is for cue/bin cdrom images with compressed (ogg) audio tracks. We will be adding the libvorbis, libogg, and sdl_sound libraries.
* Download libogg from here http://downloads.xiph.org/releases/ogg/libogg-1.3.2.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libogg-1.3.2.tar.gz
* Configure the library, disabling shared library files
cd libogg-1.3.2
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download libvorbis from here http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.5.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libvorbis-1.3.5.tar.gz
* Configure the library, disabling shared library files
cd libvorbis-1.3.5
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download sdl_sound from here https://www.icculus.org/SDL_sound/downloads/SDL_sound-1.0.3.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_sound-1.0.3.tar.gz
* Configure and compile
cd SDL_sound-1.0.3
./configure --disable-shared --prefix=/mingw LIBS="-lvorbisfile -lvorbis -logg"
make
make install
cd ..

== Enabling the debugger (You probably don't want this) ==
The debugger is mainly for developers of DOSBox, so they can find out why a game isn't working.
* Download the PDCurses source files from http://sourceforge.net/projects/pdcurses/files/pdcurses/3.4/PDCurses-3.4.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf PDCurses-3.4.tar.gz
* Compile the library
cd PDCurses-3.4/win32
make -f gccwin32.mak DLL=N
* And now copy the files to your /mingw folders
cp pdcurses.a /mingw/lib/libpdcurses.a
cd ..
cp curses.h panel.h /mingw/include/
cd ..

== Compiling DOSBox ==
* Download the latest official DOSBox SVN source files from here: http://source.dosbox.com/dosboxsvn.tgz
(There are also enhanced SVN versions containing additional fixes and/or features that are not officially part of DOSBox, see [[SVN Builds]] for more details)
* Copy the file to your MSYS home folder
* Extract the file
tar xvf dosboxsvn.tgz
* Let's configure DOSBox, and tell it to use the static C library (-static-libgcc) and C++ library (-static-libstdc++) and stripping the final EXE of debug information (-s)
cd dosbox
./autogen.sh
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s"
* For SDL_sound support, you have to extra some extra parameters so that the configure command knows where to find the audio library files (LIBS="-lvorbisfile.....)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg"
* If you want to enable debugging (you probably don't)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg" --enable-debug
* And now for compiling DOSBox
make
* The last step is to gather all the files together in a folder
** Create a folder with a name of your choosing
** Copy the dosbox.exe file located under the '''dosbox\src''' folder, e.g. '''C:\MinGW\msys\1.0\home\Administrator\dosbox\src''' to the folder you created
** Copy the SDL.dll file located under '''SDL-1.2.15\bin''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL-1.2.15\bin''' to the folder you created
** Optionally, copy the SDL_net.dll file located under '''SDL_net-1.2.8\.libs''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL_net-1.2.8\.libs''' to the folder you created

Start up DOSBox, and see if it works.

Building DOSBox with MinGW

2018-07-13T19:51:54Z

Rainwarrior: /* Adding screenshot support (Optional) */ libpng's configure script is currently broken with MinGW, here's a way to correct it

DOSBox is a complicated project. This document aims to provide a step by step description of how to use the MinGW developement environment to successfully build DOSBox. An alternative is to use [[Building DOSBox with Visual C 2008 Express|Microsoft Visual Studio]].

This page will guide you through setting up MinGW to compile a current (SVN/CVS) version of DOSBox. Because of updates to compilers and libraries, this guide will not work with the 0.74 (the last official release, which is currently over 6 years old) source files.

== Installing MinGW ==
* Download mingw-get-setup.exe from http://sourceforge.net/projects/mingw/
* Run the installer, choosing the defaults
* Once the '''MinGW Installation Manager''' application starts, select
** mingw-developer-toolkit (msys-base should be automatically added)
** mingw32-base
** mingw32-gcc-g++
* On the installation menu, apply changes, and confirm that you want to apply the changes

The installation manager is going to download a bunch of files, and at the end, start installing them. Once this is done, you can close the dialog box as well as the installation manager.

Well done, MinGW is now installed! Let's start it up.

* Browse to '''C:\MinGW\msys\1.0'''
* Run '''MSYS.BAT'''

This will start up a DOS prompt like screen, lets mount the base path
mount 'c:\MinGW' /mingw

You have now completed this section, lets move on to adding the SDL libraries to MinGW.

== Adding the SDL libraries to MinGW ==
* Download the pre compiled SDL development libraries from here http://www.libsdl.org/release/SDL-devel-1.2.15-mingw32.tar.gz
* Copy the downloaded file to your MSYS home folder, it's going to be something like '''C:\MinGW\msys\1.0\home\Administrator'''
* Switch back to the MSYS command prompt we started earlier
* Lets extract the downloaded files
tar xvf SDL-devel-1.2.15-mingw32.tar.gz
* And now add the files to MinGW
cd SDL-1.2.15
make install-sdl prefix=/mingw
cd ..

Cool, the SDL libraries have been added to MinGW, onto the next section.

== Adding Direct Draw support to DOSBox (Optional) ==
If you want to give DOSBox the option to use the DDRAW output option, then we need to add a couple of extra libraries to MinGW
* Download the following file, http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the files (the -C parameter, tells tar where to extract the files to)
tar xvf directx-devel.tar.gz -C /mingw

== Adding networking support to DOSBox (Optional) ==
These steps show you how to add the SDL_net libraries to MinGW, which enable networking and modem for DOSBox. If you aren't going to be using DOSBox for multi player games, then you can probably skip this step.
* Download the SDL_net source files from https://www.libsdl.org/projects/SDL_net/release/SDL_net-1.2.8.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_net-1.2.8.tar.gz
* Lets configure the libraries
cd SDL_net-1.2.8
./configure --prefix=/mingw
* SDLnet.c will have to be modified slightly to compile. Open it with a text editor and add the following #include near the top of the file:
#include <winerror.h>
* And now compile them
make
* And then install them (copy the files)
make install
cd ..

== Adding screenshot support (Optional) ==
This one is a bit tricky because it relies on two libraries, zlib (libpng needs these libraries), and libpng. We are also going to be compiling the libraries statically to keep external DLL's to a minimum.
* Download zlib from here http://sourceforge.net/projects/libpng/files/zlib/1.2.8/zlib-1.2.8.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf zlib-1.2.8.tar.xz
* Lets build the static library
cd zlib-1.2.8
make -f win32/Makefile.gcc
* And now copy the files to /mingw
cp libz.a /mingw/lib/
cp zlib.h zconf.h /mingw/include/
cd ..
Cool, that wasn't too hard, onto libpng
* Download libpng from here https://sourceforge.net/projects/libpng/files/libpng16/older-releases/1.6.18/libpng-1.6.18.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libpng-1.6.18.tar.xz
* Configure the library
cd libpng-1.6.18
./configure --disable-shared --prefix=/mingw
* There is currently [https://sourceforge.net/p/libpng/bugs/273/ a problem with the configure script] that will need to be manually resolved. Open '''pnglibconf.h''' with a text editor, and you will find several #define lines near the bottom that have been erroneously split into two lines. This can be fixed by adding a backslash to the end of the affected lines:
199: #define PNG_TEXT_Z_DEFAULT_COMPRESSION \
201: #define PNG_TEXT_Z_DEFAULT_STRATEGY \
209: #define PNG_ZLIB_VERNUM \
211: #define PNG_Z_DEFAULT_COMPRESSION \
213: #define PNG_Z_DEFAULT_NOFILTER_STRATEGY \
215: #define PNG_Z_DEFAULT_STRATEGY \
* And now to compile and install the files
make
make install
cd ..

== Adding support for compressed audio on diskimages (Optional) ==
This is for cue/bin cdrom images with compressed (ogg) audio tracks. We will be adding the libvorbis, libogg, and sdl_sound libraries.
* Download libogg from here http://downloads.xiph.org/releases/ogg/libogg-1.3.2.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libogg-1.3.2.tar.gz
* Configure the library, disabling shared library files
cd libogg-1.3.2
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download libvorbis from here http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.5.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libvorbis-1.3.5.tar.gz
* Configure the library, disabling shared library files
cd libvorbis-1.3.5
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download sdl_sound from here https://www.icculus.org/SDL_sound/downloads/SDL_sound-1.0.3.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_sound-1.0.3.tar.gz
* Configure and compile
cd SDL_sound-1.0.3
./configure --disable-shared --prefix=/mingw LIBS="-lvorbisfile -lvorbis -logg"
make
make install
cd ..

== Enabling the debugger (You probably don't want this) ==
The debugger is mainly for developers of DOSBox, so they can find out why a game isn't working.
* Download the PDCurses source files from http://sourceforge.net/projects/pdcurses/files/pdcurses/3.4/PDCurses-3.4.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf PDCurses-3.4.tar.gz
* Compile the library
cd PDCurses-3.4/win32
make -f gccwin32.mak DLL=N
* And now copy the files to your /mingw folders
cp pdcurses.a /mingw/lib/libpdcurses.a
cd ..
cp curses.h panel.h /mingw/include/
cd ..

== Compiling DOSBox ==
* Download the latest official DOSBox SVN source files from here: http://source.dosbox.com/dosboxsvn.tgz
(There are also enhanced SVN versions containing additional fixes and/or features that are not officially part of DOSBox, see [[SVN Builds]] for more details)
* Copy the file to your MSYS home folder
* Extract the file
tar xvf dosboxsvn.tgz
* Let's configure DOSBox, and tell it to use the static C library (-static-libgcc) and C++ library (-static-libstdc++) and stripping the final EXE of debug information (-s)
cd dosbox
./autogen.sh
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s"
* For SDL_sound support, you have to extra some extra parameters so that the configure command knows where to find the audio library files (LIBS="-lvorbisfile.....)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg"
* If you want to enable debugging (you probably don't)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg" --enable-debug
* And now for compiling DOSBox
make
* The last step is to gather all the files together in a folder
** Create a folder with a name of your choosing
** Copy the dosbox.exe file located under the '''dosbox\src''' folder, e.g. '''C:\MinGW\msys\1.0\home\Administrator\dosbox\src''' to the folder you created
** Copy the SDL.dll file located under '''SDL-1.2.15\bin''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL-1.2.15\bin''' to the folder you created
** Optionally, copy the SDL_net.dll file located under '''SDL_net-1.2.8\.libs''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL_net-1.2.8\.libs''' to the folder you created

Start up DOSBox, and see if it works.

Building DOSBox with MinGW

2018-07-13T19:45:28Z

Rainwarrior: /* Adding networking support to DOSBox (Optional) */ SDLnet.c will fail compilation for some windows error defines (ERROR_BUFFER_OVERLOW, NO_ERROR), this is one way to fix it (don't know a better way)

DOSBox is a complicated project. This document aims to provide a step by step description of how to use the MinGW developement environment to successfully build DOSBox. An alternative is to use [[Building DOSBox with Visual C 2008 Express|Microsoft Visual Studio]].

This page will guide you through setting up MinGW to compile a current (SVN/CVS) version of DOSBox. Because of updates to compilers and libraries, this guide will not work with the 0.74 (the last official release, which is currently over 6 years old) source files.

== Installing MinGW ==
* Download mingw-get-setup.exe from http://sourceforge.net/projects/mingw/
* Run the installer, choosing the defaults
* Once the '''MinGW Installation Manager''' application starts, select
** mingw-developer-toolkit (msys-base should be automatically added)
** mingw32-base
** mingw32-gcc-g++
* On the installation menu, apply changes, and confirm that you want to apply the changes

The installation manager is going to download a bunch of files, and at the end, start installing them. Once this is done, you can close the dialog box as well as the installation manager.

Well done, MinGW is now installed! Let's start it up.

* Browse to '''C:\MinGW\msys\1.0'''
* Run '''MSYS.BAT'''

This will start up a DOS prompt like screen, lets mount the base path
mount 'c:\MinGW' /mingw

You have now completed this section, lets move on to adding the SDL libraries to MinGW.

== Adding the SDL libraries to MinGW ==
* Download the pre compiled SDL development libraries from here http://www.libsdl.org/release/SDL-devel-1.2.15-mingw32.tar.gz
* Copy the downloaded file to your MSYS home folder, it's going to be something like '''C:\MinGW\msys\1.0\home\Administrator'''
* Switch back to the MSYS command prompt we started earlier
* Lets extract the downloaded files
tar xvf SDL-devel-1.2.15-mingw32.tar.gz
* And now add the files to MinGW
cd SDL-1.2.15
make install-sdl prefix=/mingw
cd ..

Cool, the SDL libraries have been added to MinGW, onto the next section.

== Adding Direct Draw support to DOSBox (Optional) ==
If you want to give DOSBox the option to use the DDRAW output option, then we need to add a couple of extra libraries to MinGW
* Download the following file, http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the files (the -C parameter, tells tar where to extract the files to)
tar xvf directx-devel.tar.gz -C /mingw

== Adding networking support to DOSBox (Optional) ==
These steps show you how to add the SDL_net libraries to MinGW, which enable networking and modem for DOSBox. If you aren't going to be using DOSBox for multi player games, then you can probably skip this step.
* Download the SDL_net source files from https://www.libsdl.org/projects/SDL_net/release/SDL_net-1.2.8.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_net-1.2.8.tar.gz
* Lets configure the libraries
cd SDL_net-1.2.8
./configure --prefix=/mingw
* SDLnet.c will have to be modified slightly to compile. Open it with a text editor and add the following #include near the top of the file:
#include <winerror.h>
* And now compile them
make
* And then install them (copy the files)
make install
cd ..

== Adding screenshot support (Optional) ==
This one is a bit tricky because it relies on two libraries, zlib (libpng needs these libraries), and libpng. We are also going to be compiling the libraries statically to keep external DLL's to a minimum.
* Download zlib from here http://sourceforge.net/projects/libpng/files/zlib/1.2.8/zlib-1.2.8.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf zlib-1.2.8.tar.xz
* Lets build the static library
cd zlib-1.2.8
make -f win32/Makefile.gcc
* And now copy the files to /mingw
cp libz.a /mingw/lib/
cp zlib.h zconf.h /mingw/include/
cd ..
Cool, that wasn't too hard, onto libpng
* Download libpng from here https://sourceforge.net/projects/libpng/files/libpng16/older-releases/1.6.18/libpng-1.6.18.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libpng-1.6.18.tar.xz
* Configure the library
cd libpng-1.6.18
./configure --disable-shared --prefix=/mingw
* And now to compile and install the files
make
make install
cd ..

== Adding support for compressed audio on diskimages (Optional) ==
This is for cue/bin cdrom images with compressed (ogg) audio tracks. We will be adding the libvorbis, libogg, and sdl_sound libraries.
* Download libogg from here http://downloads.xiph.org/releases/ogg/libogg-1.3.2.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libogg-1.3.2.tar.gz
* Configure the library, disabling shared library files
cd libogg-1.3.2
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download libvorbis from here http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.5.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libvorbis-1.3.5.tar.gz
* Configure the library, disabling shared library files
cd libvorbis-1.3.5
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download sdl_sound from here https://www.icculus.org/SDL_sound/downloads/SDL_sound-1.0.3.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_sound-1.0.3.tar.gz
* Configure and compile
cd SDL_sound-1.0.3
./configure --disable-shared --prefix=/mingw LIBS="-lvorbisfile -lvorbis -logg"
make
make install
cd ..

== Enabling the debugger (You probably don't want this) ==
The debugger is mainly for developers of DOSBox, so they can find out why a game isn't working.
* Download the PDCurses source files from http://sourceforge.net/projects/pdcurses/files/pdcurses/3.4/PDCurses-3.4.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf PDCurses-3.4.tar.gz
* Compile the library
cd PDCurses-3.4/win32
make -f gccwin32.mak DLL=N
* And now copy the files to your /mingw folders
cp pdcurses.a /mingw/lib/libpdcurses.a
cd ..
cp curses.h panel.h /mingw/include/
cd ..

== Compiling DOSBox ==
* Download the latest official DOSBox SVN source files from here: http://source.dosbox.com/dosboxsvn.tgz
(There are also enhanced SVN versions containing additional fixes and/or features that are not officially part of DOSBox, see [[SVN Builds]] for more details)
* Copy the file to your MSYS home folder
* Extract the file
tar xvf dosboxsvn.tgz
* Let's configure DOSBox, and tell it to use the static C library (-static-libgcc) and C++ library (-static-libstdc++) and stripping the final EXE of debug information (-s)
cd dosbox
./autogen.sh
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s"
* For SDL_sound support, you have to extra some extra parameters so that the configure command knows where to find the audio library files (LIBS="-lvorbisfile.....)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg"
* If you want to enable debugging (you probably don't)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg" --enable-debug
* And now for compiling DOSBox
make
* The last step is to gather all the files together in a folder
** Create a folder with a name of your choosing
** Copy the dosbox.exe file located under the '''dosbox\src''' folder, e.g. '''C:\MinGW\msys\1.0\home\Administrator\dosbox\src''' to the folder you created
** Copy the SDL.dll file located under '''SDL-1.2.15\bin''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL-1.2.15\bin''' to the folder you created
** Optionally, copy the SDL_net.dll file located under '''SDL_net-1.2.8\.libs''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL_net-1.2.8\.libs''' to the folder you created

Start up DOSBox, and see if it works.

Building DOSBox with MinGW

2018-07-13T19:40:31Z

Rainwarrior: /* Adding screenshot support (Optional) */ libpng-1.6.18 has moved to older-releases folder, using xz for updated link because it's smaller

DOSBox is a complicated project. This document aims to provide a step by step description of how to use the MinGW developement environment to successfully build DOSBox. An alternative is to use [[Building DOSBox with Visual C 2008 Express|Microsoft Visual Studio]].

This page will guide you through setting up MinGW to compile a current (SVN/CVS) version of DOSBox. Because of updates to compilers and libraries, this guide will not work with the 0.74 (the last official release, which is currently over 6 years old) source files.

== Installing MinGW ==
* Download mingw-get-setup.exe from http://sourceforge.net/projects/mingw/
* Run the installer, choosing the defaults
* Once the '''MinGW Installation Manager''' application starts, select
** mingw-developer-toolkit (msys-base should be automatically added)
** mingw32-base
** mingw32-gcc-g++
* On the installation menu, apply changes, and confirm that you want to apply the changes

The installation manager is going to download a bunch of files, and at the end, start installing them. Once this is done, you can close the dialog box as well as the installation manager.

Well done, MinGW is now installed! Let's start it up.

* Browse to '''C:\MinGW\msys\1.0'''
* Run '''MSYS.BAT'''

This will start up a DOS prompt like screen, lets mount the base path
mount 'c:\MinGW' /mingw

You have now completed this section, lets move on to adding the SDL libraries to MinGW.

== Adding the SDL libraries to MinGW ==
* Download the pre compiled SDL development libraries from here http://www.libsdl.org/release/SDL-devel-1.2.15-mingw32.tar.gz
* Copy the downloaded file to your MSYS home folder, it's going to be something like '''C:\MinGW\msys\1.0\home\Administrator'''
* Switch back to the MSYS command prompt we started earlier
* Lets extract the downloaded files
tar xvf SDL-devel-1.2.15-mingw32.tar.gz
* And now add the files to MinGW
cd SDL-1.2.15
make install-sdl prefix=/mingw
cd ..

Cool, the SDL libraries have been added to MinGW, onto the next section.

== Adding Direct Draw support to DOSBox (Optional) ==
If you want to give DOSBox the option to use the DDRAW output option, then we need to add a couple of extra libraries to MinGW
* Download the following file, http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the files (the -C parameter, tells tar where to extract the files to)
tar xvf directx-devel.tar.gz -C /mingw

== Adding networking support to DOSBox (Optional) ==
These steps show you how to add the SDL_net libraries to MinGW, which enable networking and modem for DOSBox. If you aren't going to be using DOSBox for multi player games, then you can probably skip this step.
* Download the SDL_net source files from https://www.libsdl.org/projects/SDL_net/release/SDL_net-1.2.8.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_net-1.2.8.tar.gz
* Lets configure the libraries
cd SDL_net-1.2.8
./configure --prefix=/mingw
* And now compile them
make
* And then install them (copy the files)
make install
cd ..

== Adding screenshot support (Optional) ==
This one is a bit tricky because it relies on two libraries, zlib (libpng needs these libraries), and libpng. We are also going to be compiling the libraries statically to keep external DLL's to a minimum.
* Download zlib from here http://sourceforge.net/projects/libpng/files/zlib/1.2.8/zlib-1.2.8.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf zlib-1.2.8.tar.xz
* Lets build the static library
cd zlib-1.2.8
make -f win32/Makefile.gcc
* And now copy the files to /mingw
cp libz.a /mingw/lib/
cp zlib.h zconf.h /mingw/include/
cd ..
Cool, that wasn't too hard, onto libpng
* Download libpng from here https://sourceforge.net/projects/libpng/files/libpng16/older-releases/1.6.18/libpng-1.6.18.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libpng-1.6.18.tar.xz
* Configure the library
cd libpng-1.6.18
./configure --disable-shared --prefix=/mingw
* And now to compile and install the files
make
make install
cd ..

== Adding support for compressed audio on diskimages (Optional) ==
This is for cue/bin cdrom images with compressed (ogg) audio tracks. We will be adding the libvorbis, libogg, and sdl_sound libraries.
* Download libogg from here http://downloads.xiph.org/releases/ogg/libogg-1.3.2.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libogg-1.3.2.tar.gz
* Configure the library, disabling shared library files
cd libogg-1.3.2
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download libvorbis from here http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.5.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libvorbis-1.3.5.tar.gz
* Configure the library, disabling shared library files
cd libvorbis-1.3.5
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download sdl_sound from here https://www.icculus.org/SDL_sound/downloads/SDL_sound-1.0.3.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_sound-1.0.3.tar.gz
* Configure and compile
cd SDL_sound-1.0.3
./configure --disable-shared --prefix=/mingw LIBS="-lvorbisfile -lvorbis -logg"
make
make install
cd ..

== Enabling the debugger (You probably don't want this) ==
The debugger is mainly for developers of DOSBox, so they can find out why a game isn't working.
* Download the PDCurses source files from http://sourceforge.net/projects/pdcurses/files/pdcurses/3.4/PDCurses-3.4.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf PDCurses-3.4.tar.gz
* Compile the library
cd PDCurses-3.4/win32
make -f gccwin32.mak DLL=N
* And now copy the files to your /mingw folders
cp pdcurses.a /mingw/lib/libpdcurses.a
cd ..
cp curses.h panel.h /mingw/include/
cd ..

== Compiling DOSBox ==
* Download the latest official DOSBox SVN source files from here: http://source.dosbox.com/dosboxsvn.tgz
(There are also enhanced SVN versions containing additional fixes and/or features that are not officially part of DOSBox, see [[SVN Builds]] for more details)
* Copy the file to your MSYS home folder
* Extract the file
tar xvf dosboxsvn.tgz
* Let's configure DOSBox, and tell it to use the static C library (-static-libgcc) and C++ library (-static-libstdc++) and stripping the final EXE of debug information (-s)
cd dosbox
./autogen.sh
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s"
* For SDL_sound support, you have to extra some extra parameters so that the configure command knows where to find the audio library files (LIBS="-lvorbisfile.....)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg"
* If you want to enable debugging (you probably don't)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg" --enable-debug
* And now for compiling DOSBox
make
* The last step is to gather all the files together in a folder
** Create a folder with a name of your choosing
** Copy the dosbox.exe file located under the '''dosbox\src''' folder, e.g. '''C:\MinGW\msys\1.0\home\Administrator\dosbox\src''' to the folder you created
** Copy the SDL.dll file located under '''SDL-1.2.15\bin''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL-1.2.15\bin''' to the folder you created
** Optionally, copy the SDL_net.dll file located under '''SDL_net-1.2.8\.libs''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL_net-1.2.8\.libs''' to the folder you created

Start up DOSBox, and see if it works.

Building DOSBox with MinGW

2018-07-13T19:38:15Z

Rainwarrior: /* Adding support for compressed audio on diskimages (Optional) */ SDL_sound vs MinGW no longer appears to have this compile issue

DOSBox is a complicated project. This document aims to provide a step by step description of how to use the MinGW developement environment to successfully build DOSBox. An alternative is to use [[Building DOSBox with Visual C 2008 Express|Microsoft Visual Studio]].

This page will guide you through setting up MinGW to compile a current (SVN/CVS) version of DOSBox. Because of updates to compilers and libraries, this guide will not work with the 0.74 (the last official release, which is currently over 6 years old) source files.

== Installing MinGW ==
* Download mingw-get-setup.exe from http://sourceforge.net/projects/mingw/
* Run the installer, choosing the defaults
* Once the '''MinGW Installation Manager''' application starts, select
** mingw-developer-toolkit (msys-base should be automatically added)
** mingw32-base
** mingw32-gcc-g++
* On the installation menu, apply changes, and confirm that you want to apply the changes

The installation manager is going to download a bunch of files, and at the end, start installing them. Once this is done, you can close the dialog box as well as the installation manager.

Well done, MinGW is now installed! Let's start it up.

* Browse to '''C:\MinGW\msys\1.0'''
* Run '''MSYS.BAT'''

This will start up a DOS prompt like screen, lets mount the base path
mount 'c:\MinGW' /mingw

You have now completed this section, lets move on to adding the SDL libraries to MinGW.

== Adding the SDL libraries to MinGW ==
* Download the pre compiled SDL development libraries from here http://www.libsdl.org/release/SDL-devel-1.2.15-mingw32.tar.gz
* Copy the downloaded file to your MSYS home folder, it's going to be something like '''C:\MinGW\msys\1.0\home\Administrator'''
* Switch back to the MSYS command prompt we started earlier
* Lets extract the downloaded files
tar xvf SDL-devel-1.2.15-mingw32.tar.gz
* And now add the files to MinGW
cd SDL-1.2.15
make install-sdl prefix=/mingw
cd ..

Cool, the SDL libraries have been added to MinGW, onto the next section.

== Adding Direct Draw support to DOSBox (Optional) ==
If you want to give DOSBox the option to use the DDRAW output option, then we need to add a couple of extra libraries to MinGW
* Download the following file, http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the files (the -C parameter, tells tar where to extract the files to)
tar xvf directx-devel.tar.gz -C /mingw

== Adding networking support to DOSBox (Optional) ==
These steps show you how to add the SDL_net libraries to MinGW, which enable networking and modem for DOSBox. If you aren't going to be using DOSBox for multi player games, then you can probably skip this step.
* Download the SDL_net source files from https://www.libsdl.org/projects/SDL_net/release/SDL_net-1.2.8.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_net-1.2.8.tar.gz
* Lets configure the libraries
cd SDL_net-1.2.8
./configure --prefix=/mingw
* And now compile them
make
* And then install them (copy the files)
make install
cd ..

== Adding screenshot support (Optional) ==
This one is a bit tricky because it relies on two libraries, zlib (libpng needs these libraries), and libpng. We are also going to be compiling the libraries statically to keep external DLL's to a minimum.
* Download zlib from here http://sourceforge.net/projects/libpng/files/zlib/1.2.8/zlib-1.2.8.tar.xz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf zlib-1.2.8.tar.xz
* Lets build the static library
cd zlib-1.2.8
make -f win32/Makefile.gcc
* And now copy the files to /mingw
cp libz.a /mingw/lib/
cp zlib.h zconf.h /mingw/include/
cd ..
Cool, that wasn't too hard, onto libpng
* Download libpng from here http://sourceforge.net/projects/libpng/files/libpng16/1.6.18/libpng-1.6.18.tar.gz/download
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libpng-1.6.18.tar.gz
* Configure the library
cd libpng-1.6.18
./configure --disable-shared --prefix=/mingw
* And now to compile and install the files
make
make install
cd ..

== Adding support for compressed audio on diskimages (Optional) ==
This is for cue/bin cdrom images with compressed (ogg) audio tracks. We will be adding the libvorbis, libogg, and sdl_sound libraries.
* Download libogg from here http://downloads.xiph.org/releases/ogg/libogg-1.3.2.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libogg-1.3.2.tar.gz
* Configure the library, disabling shared library files
cd libogg-1.3.2
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download libvorbis from here http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.5.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf libvorbis-1.3.5.tar.gz
* Configure the library, disabling shared library files
cd libvorbis-1.3.5
./configure --disable-shared --prefix=/mingw
* Compile and install the library files
make
make install
cd ..

* Download sdl_sound from here https://www.icculus.org/SDL_sound/downloads/SDL_sound-1.0.3.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf SDL_sound-1.0.3.tar.gz
* Configure and compile
cd SDL_sound-1.0.3
./configure --disable-shared --prefix=/mingw LIBS="-lvorbisfile -lvorbis -logg"
make
make install
cd ..

== Enabling the debugger (You probably don't want this) ==
The debugger is mainly for developers of DOSBox, so they can find out why a game isn't working.
* Download the PDCurses source files from http://sourceforge.net/projects/pdcurses/files/pdcurses/3.4/PDCurses-3.4.tar.gz
* Copy the downloaded file to your MSYS home folder
* Switch to the MSYS command prompt
* Extract the file
tar xvf PDCurses-3.4.tar.gz
* Compile the library
cd PDCurses-3.4/win32
make -f gccwin32.mak DLL=N
* And now copy the files to your /mingw folders
cp pdcurses.a /mingw/lib/libpdcurses.a
cd ..
cp curses.h panel.h /mingw/include/
cd ..

== Compiling DOSBox ==
* Download the latest official DOSBox SVN source files from here: http://source.dosbox.com/dosboxsvn.tgz
(There are also enhanced SVN versions containing additional fixes and/or features that are not officially part of DOSBox, see [[SVN Builds]] for more details)
* Copy the file to your MSYS home folder
* Extract the file
tar xvf dosboxsvn.tgz
* Let's configure DOSBox, and tell it to use the static C library (-static-libgcc) and C++ library (-static-libstdc++) and stripping the final EXE of debug information (-s)
cd dosbox
./autogen.sh
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s"
* For SDL_sound support, you have to extra some extra parameters so that the configure command knows where to find the audio library files (LIBS="-lvorbisfile.....)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg"
* If you want to enable debugging (you probably don't)
./configure --enable-core-inline LDFLAGS="-static-libgcc -static-libstdc++ -s" LIBS="-lvorbisfile -lvorbis -logg" --enable-debug
* And now for compiling DOSBox
make
* The last step is to gather all the files together in a folder
** Create a folder with a name of your choosing
** Copy the dosbox.exe file located under the '''dosbox\src''' folder, e.g. '''C:\MinGW\msys\1.0\home\Administrator\dosbox\src''' to the folder you created
** Copy the SDL.dll file located under '''SDL-1.2.15\bin''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL-1.2.15\bin''' to the folder you created
** Optionally, copy the SDL_net.dll file located under '''SDL_net-1.2.8\.libs''', e.g. '''C:\MinGW\msys\1.0\home\Administrator\SDL_net-1.2.8\.libs''' to the folder you created

Start up DOSBox, and see if it works.