Difference between revisions of "Building DOSBox with MinGW"

From DOSBoxWiki
Jump to navigationJump to search
Line 1: Line 1:
As nobody has yet ported the original page (http://dosbox.sourceforge.net/wiki/index.php?page=BuildingDOSBox) I've done it.
+
== Building your own version of DOSBox ==
<br><br>
+
 
<br><br>
+
=== 1. Grab the source ===
<br>Building your own version of DOSBox
+
 
<br>1. Grab the source
+
First, grab the latest version of the DOSbox sourcecode. A fairly often updated CVS-Dump can be found at: http://dosbox.linuxdevel.net/dosboxcvs.tgz
<br>
+
 
<br>First, grab the latest version of the DOSbox sourcecode. A fairly often updated CVS-Dump can be found at: http://dosbox.linuxdevel.net/dosboxcvs.tgz
+
Download it and extract it to a seperate directory.
<br>
+
 
<br>Download it and extract it to a seperate directory.
+
=== 2. SDL ===
<br>2. SDL
+
 
<br>
+
DOSBox utilizes SDL (Simple DirectMedia Layer) to use your graphics and sound-hardware. Ergo, you'll need to download it as well. Grab the latest source at
<br>DOSBox utilizes SDL (Simple DirectMedia Layer) to use your graphics and sound-hardware. Ergo, you'll need to download it as well. Grab the latest source at
+
 
<br>http://www.libsdl.org/  
+
: http://www.libsdl.org/
<br>
+
 
<br>and extract to a seperate directory.
+
and extract to a seperate directory.
<br>
+
 
<br>When working on Windows, you might want to save a lot of effort and just use the SDL (and optionally SDL_net) .DLL files included with the latest official DOSBox release, as compiling SDL with full options (e.g. DirectX support) is a bit involved. There are also pre-built .DLL files on the SDL web site (Runtime Libraries -> Win32) that you can try at
+
When working on Windows, you might want to save a lot of effort and just use the SDL (and optionally SDL_net) .DLL files included with the latest official DOSBox release, as compiling SDL with full options (e.g. DirectX support) is a bit involved. There are also pre-built .DLL files on the SDL web site (Runtime Libraries -> Win32) that you can try at
<br>http://www.libsdl.org/download-1.2.php  
+
 
<br>
+
: http://www.libsdl.org/download-1.2.php
<br>Note that as of 12 Dec 2004, ddraw (DirectDraw) rendering mode will not work in DOSBox unless you either use the SDL.dll included with the latest version of DOSBox, or build your own SDL.dll with the changes mentioned in the "Compiling SDL" section below.
+
 
<br>3. Compiling enviroment
+
Note that as of 12 Dec 2004, ddraw (DirectDraw) rendering mode will not work in DOSBox unless you either use the SDL.dll included with the latest version of DOSBox, or build your own SDL.dll with the changes mentioned in the "Compiling SDL" section below.
<br>
+
 
<br>When working on Windows, you'll most likely need a compiling enviroment. We suggest using the combination of MiniGW and MSYS, which can be found at
+
=== 3. Compiling enviroment ===
<br>http://prdownloads.sf.net/mingw/  
+
 
<br>
+
When working on Windows, you'll most likely need a compiling enviroment. We suggest using the combination of MiniGW and MSYS, which can be found at
<br>You'll need to download both the latest MiniGW and MSYS. After downloading install MiniGW and MSYS (in this order). The MSYS-Installer should ask for the installation directory of MiniGW, so you should pick the path where you installed it. After the installation, run the MSYS.BAT and you should see a unix-like command prompt.  
+
 
<br>4. Compiling SDL
+
: http://prdownloads.sf.net/mingw/
<br>
+
 
<br>Navigate to the directory where you extracted the SDL-source (using unix commands) and type
+
You'll need to download both the latest MiniGW and MSYS. After downloading install MiniGW and MSYS (in this order). The MSYS-Installer should ask for the installation directory of MiniGW, so you should pick the path where you installed it. After the installation, run the MSYS.BAT and you should see a unix-like command prompt.  
<br>./configure  
+
 
<br>make  
+
=== 4. Compiling SDL ===
<br>make install  
+
 
<br>
+
Navigate to the directory where you extracted the SDL-source (using unix commands) and type
<br>Some MinGW-specific info on compiling SDL under Windows is available at
+
 
<br>http://www.libsdl.org/extras/win32/mingw32/README.txt  
+
: {{ ./configure     \\
<br>
+
    make             \\
<br>If you are having trouble with a message like 'no acceptable ld found in $PATH' try 'export LD=/c/gxx-2.95.2/bin/ld.exe' (or wherever you have the exe; GCC 2.95 in this case)
+
    make install     }}
<br>
+
 
<br>Also, if you have trouble getting ddraw (DirectDraw) working in DOSBox, see this post on the DOSBox forum for a possible fix:
+
Some MinGW-specific info on compiling SDL under Windows is available at
<br>http://vogons.zetafleet.com/viewtopic.php?p=48050&highlight=#48050  
+
 
<br>4b. SDL-net (optional)
+
: http://www.libsdl.org/extras/win32/mingw32/README.txt
<br>
+
 
<br>If you want to benefit from DOSBox'es Modem-Emulation or IPX-Support, you'll additionally need the SDL-net library, which can be found at
+
If you are having trouble with a message like 'no acceptable ld found in $PATH' try 'export LD=/c/gxx-2.95.2/bin/ld.exe' (or wherever you have the exe; GCC 2.95 in this case)
<br>http://www.libsdl.org/projects/SDL_net/  
+
 
<br>
+
Also, if you have trouble getting ddraw (DirectDraw) working in DOSBox, see this post on the DOSBox forum for a possible fix:
<br>Download, extract and compile as you did with SDL.
+
 
<br>
+
: http://vogons.zetafleet.com/viewtopic.php?p=48050&highlight=#48050
<br>If you skipped building your own SDL.dll, you can use the one included with the latest official release of DOSBox or you can get a SDL_net win32 binary (.DLL) release on the SDL web site at the URL above.
+
 
<br>5. Compiling DOSBox
+
==== 4b. SDL-net (optional) ====
<br>
+
 
<br>After compiling you'll need to adjust the PATH variable to point at the directory where the freshly built SDL-Library can be found.
+
If you want to benefit from DOSBox'es Modem-Emulation or IPX-Support, you'll additionally need the SDL-net library, which can be found at
<br>
+
 
<br>Note: if you want to use SDL-net, do the same with that library.
+
: http://www.libsdl.org/projects/SDL_net/
<br>
+
 
<br>Then, change to the directory where you extracted the DOSBox-Source and type
+
Download, extract and compile as you did with SDL.
<br>./configure  
+
 
<br>make  
+
If you skipped building your own SDL.dll, you can use the one included with the latest official release of DOSBox or you can get a SDL_net win32 binary (.DLL) release on the SDL web site at the URL above.
<br>
+
 
<br>to compile DOSBox. If everything worked, you should have a DOSBOX.EXE in the ./src - directory.
+
=== 5. Compiling DOSBox ===
<br>6. Running
+
 
<br>
+
After compiling you'll need to adjust the PATH variable to point at the directory where the freshly built SDL-Library can be found.
<br>The easiest way to run the new executable is to copy it (and your fresh SDL.dll and maybe even the SDL_net.dll) to the installation-directory of a non-CVS-version of DOSBox. That way, you have the needed directory structure and configuration files.
+
 
<br>Example for Building DosBOX 7.1 on OpenSUSE 10.2 Linux
+
//Note: if you want to use SDL-net, do the same with that library.//
<br>
+
 
<br>NOTE: configure flags need double dashes in front of them. Couldn't show this due to wiki formatting restrictions.
+
Then, change to the directory where you extracted the DOSBox-Source and type
<br>
+
 
<br>-Remove the existing dosbox version if you have it.
+
: {{ ./configure \\
<br>
+
    make         }}
<br>-Obtain and extract the dosbox source code.
+
 
<br>
+
to compile DOSBox. If everything worked, you should have a {{DOSBOX.EXE}} in the {{./src}} - directory.
<br>-SUSE linux 10.2 already has SDL and alsa installed, but you need to install the SDL-devel package and alsa-devel package (for header files and libs).
+
 
<br>
+
=== 6. Running ===
<br>-Obtain the SDL_Sound src from http://icculus.org/SDL_sound/downloads. Extract the source somewhere.
+
 
<br>
+
The easiest way to run the new executable is to copy it (and your fresh {{SDL.dll}} //and maybe even the SDL_net.dll//) to the installation-directory of a non-CVS-version of DOSBox. That way, you have the needed directory structure and configuration files.
<br>Run configure -with-sdl-prefix=/usr/lib64 -with-sdl-exec-prefix=/usr
+
 
<br>
+
=== Example for Building DosBOX 7.1 on OpenSUSE 10.2 Linux ===
<br>make
+
 
<br>
+
NOTE: configure flags need double dashes in front of them. Couldn't show this due to wiki formatting restrictions.
<br>make install (need to be root)
+
 
<br>
+
-Remove the existing dosbox version if you have it.
<br>-OK, now you have everything you need to compile dosbox. cd to your dosbox directory, then run this at the shell:
+
 
<br>
+
-Obtain and extract the dosbox source code.
<br>export CPPFLAGS="-I/usr/local/include/SDL"
+
 
<br>
+
-SUSE linux 10.2 already has SDL and alsa installed, but you need to install the SDL-devel package and alsa-devel package (for header files and libs).
<br>export LDFLAGS="-L/usr/local/lib"
+
 
<br>
+
-Obtain the SDL_Sound src from http://icculus.org/SDL_sound/downloads. Extract the source somewhere.
<br>configure -with-sdl-prefix=/usr/lib64 -with-sdl-exec-prefix=/usr -with-alsa-prefix=/usr/lib64
+
Run configure -with-sdl-prefix=/usr/lib64 -with-sdl-exec-prefix=/usr
<br>
+
make
<br>-with-alsa-inc-prefix=/usr/include/alsa
+
make install (need to be root)
<br>
+
 
<br>make
+
-OK, now you have everything you need to compile dosbox. cd to your dosbox directory, then run this at the shell:
<br>
+
export CPPFLAGS="-I/usr/local/include/SDL"
<br>make install (need to be root).
+
export LDFLAGS="-L/usr/local/lib"
<br>
+
configure -with-sdl-prefix=/usr/lib64 -with-sdl-exec-prefix=/usr -with-alsa-prefix=/usr/lib64
<br>-The reason for the shell variables is that it seemed to be the only way configure could find the files it needed. There aren't any config options to find the SDL_sound library, and I tried giving it -libdir= and -includedir=, but that didn't work.
+
    -with-alsa-inc-prefix=/usr/include/alsa
<br>
+
make
 +
make install (need to be root).
 +
 
 +
-The reason for the shell variables is that it seemed to be the only way configure could find the files it needed. There aren't any config options to find the SDL_sound library, and I tried giving it -libdir= and -includedir=, but that didn't work.

Revision as of 06:24, 20 December 2007

Building your own version of DOSBox

1. Grab the source

First, grab the latest version of the DOSbox sourcecode. A fairly often updated CVS-Dump can be found at: http://dosbox.linuxdevel.net/dosboxcvs.tgz

Download it and extract it to a seperate directory.

2. SDL

DOSBox utilizes SDL (Simple DirectMedia Layer) to use your graphics and sound-hardware. Ergo, you'll need to download it as well. Grab the latest source at

http://www.libsdl.org/

and extract to a seperate directory.

When working on Windows, you might want to save a lot of effort and just use the SDL (and optionally SDL_net) .DLL files included with the latest official DOSBox release, as compiling SDL with full options (e.g. DirectX support) is a bit involved. There are also pre-built .DLL files on the SDL web site (Runtime Libraries -> Win32) that you can try at

http://www.libsdl.org/download-1.2.php

Note that as of 12 Dec 2004, ddraw (DirectDraw) rendering mode will not work in DOSBox unless you either use the SDL.dll included with the latest version of DOSBox, or build your own SDL.dll with the changes mentioned in the "Compiling SDL" section below.

3. Compiling enviroment

When working on Windows, you'll most likely need a compiling enviroment. We suggest using the combination of MiniGW and MSYS, which can be found at

http://prdownloads.sf.net/mingw/

You'll need to download both the latest MiniGW and MSYS. After downloading install MiniGW and MSYS (in this order). The MSYS-Installer should ask for the installation directory of MiniGW, so you should pick the path where you installed it. After the installation, run the MSYS.BAT and you should see a unix-like command prompt.

4. Compiling SDL

Navigate to the directory where you extracted the SDL-source (using unix commands) and type

{{ ./configure \\
    make             \\
    make install     }}

Some MinGW-specific info on compiling SDL under Windows is available at

http://www.libsdl.org/extras/win32/mingw32/README.txt

If you are having trouble with a message like 'no acceptable ld found in $PATH' try 'export LD=/c/gxx-2.95.2/bin/ld.exe' (or wherever you have the exe; GCC 2.95 in this case)

Also, if you have trouble getting ddraw (DirectDraw) working in DOSBox, see this post on the DOSBox forum for a possible fix:

http://vogons.zetafleet.com/viewtopic.php?p=48050&highlight=#48050

4b. SDL-net (optional)

If you want to benefit from DOSBox'es Modem-Emulation or IPX-Support, you'll additionally need the SDL-net library, which can be found at

http://www.libsdl.org/projects/SDL_net/

Download, extract and compile as you did with SDL.

If you skipped building your own SDL.dll, you can use the one included with the latest official release of DOSBox or you can get a SDL_net win32 binary (.DLL) release on the SDL web site at the URL above.

5. Compiling DOSBox

After compiling you'll need to adjust the PATH variable to point at the directory where the freshly built SDL-Library can be found.

//Note: if you want to use SDL-net, do the same with that library.//

Then, change to the directory where you extracted the DOSBox-Source and type

{{ ./configure \\
   make         }}

to compile DOSBox. If everything worked, you should have a Template:DOSBOX.EXE in the {{./src}} - directory.

6. Running

The easiest way to run the new executable is to copy it (and your fresh Template:SDL.dll //and maybe even the SDL_net.dll//) to the installation-directory of a non-CVS-version of DOSBox. That way, you have the needed directory structure and configuration files.

Example for Building DosBOX 7.1 on OpenSUSE 10.2 Linux

NOTE: configure flags need double dashes in front of them. Couldn't show this due to wiki formatting restrictions.

-Remove the existing dosbox version if you have it.

-Obtain and extract the dosbox source code.

-SUSE linux 10.2 already has SDL and alsa installed, but you need to install the SDL-devel package and alsa-devel package (for header files and libs).

-Obtain the SDL_Sound src from http://icculus.org/SDL_sound/downloads. Extract the source somewhere.

Run configure -with-sdl-prefix=/usr/lib64 -with-sdl-exec-prefix=/usr
make
make install (need to be root)

-OK, now you have everything you need to compile dosbox. cd to your dosbox directory, then run this at the shell:

export CPPFLAGS="-I/usr/local/include/SDL"
export LDFLAGS="-L/usr/local/lib"
configure -with-sdl-prefix=/usr/lib64 -with-sdl-exec-prefix=/usr -with-alsa-prefix=/usr/lib64
   -with-alsa-inc-prefix=/usr/include/alsa
make
make install (need to be root).

-The reason for the shell variables is that it seemed to be the only way configure could find the files it needed. There aren't any config options to find the SDL_sound library, and I tried giving it -libdir= and -includedir=, but that didn't work.