1
0
Fork 0
No description
Find a file
Patryk Obara 03e94559e9 Rename directory with Visual Studio solution
Name 'visualc_net' invokes old names for Visual Studio
(Visual Studio .NET 2002 or 2003), which has no relation to content of
this subdirectory.

Also, by renaming this directory we mitigate chance, that during
merge-in from svn/trunk git will automatically inject some values from
from upstream, incompatible version of solution files. By sheer
luck this might happen without causing a conflict. Never happened so
far, but there's no point in risking it.
2019-12-09 07:22:15 +01:00
.github Rename directory with Visual Studio solution 2019-12-09 07:22:15 +01:00
contrib Contribute a static-opus builder 2019-11-28 09:41:43 +01:00
docs Create package-specific README file 2019-12-05 23:35:15 +01:00
include Explicitly delete copy and assignment operators 2019-12-07 21:07:38 +01:00
scripts Use PRIuPTR and define it for Windows GCC 64-bit 2019-12-03 05:12:28 +01:00
src Memory overrun and C++11 updates 2019-12-07 19:08:47 +01:00
vs Rename directory with Visual Studio solution 2019-12-09 07:22:15 +01:00
.gitignore Refactor the build and list-packages scripts 2019-11-24 15:16:44 +01:00
.pylint Allow maximum-issues to be set via command-line 2019-11-24 15:16:44 +01:00
acinclude.m4 Move definition out of autoconfig 2019-12-03 05:12:28 +01:00
AUTHORS Update authors 2010-04-20 12:51:03 +00:00
autogen.sh Allow less beautiful version numbers. 2007-02-04 10:46:34 +00:00
configure.ac Rename directory with Visual Studio solution 2019-12-09 07:22:15 +01:00
COPYING Update year and address of FSF 2019-01-25 14:09:58 +00:00
INSTALL Document the project in README.md 2019-11-28 13:38:12 +01:00
Makefile.am Rename directory with Visual Studio solution 2019-12-09 07:22:15 +01:00
README <erge 0.74-2 documentation changes into trunk 2018-08-31 17:43:09 +00:00
README.md Rename directory with Visual Studio solution 2019-12-09 07:22:15 +01:00
THANKS Updated 2010-05-09 11:07:51 +00:00

dosbox-staging

This repository attempts to modernize the DOSBox project by using current development practices and tools, fixing issues, adding features that better support today's systems, and sending patches upstream. Read more at Vogons thread.

Summary of differences compared to upstream:

dosbox-staging DOSBox
Version control Git SVN
Language C++11 C++031
CI Yes No
Static analysis Yes2,3 No
Dynamic analysis Yes No
Automated regression tests No (planned)4 No
SDL 1.2 (2.0 WIP)5 1.2

Codecs supported for CD Digital Audio emulation (loading CD music via cue sheets):

dosbox-staging DOSBox
Opus Yes (libopus) No
OGG/Vorbis Yes (built-in) Yes - SDL_sound 1.2 (libvorbis)6,
MP3 Yes (built-in) Yes - SDL_sound 1.2 (libmpg123)6,
FLAC Yes (built-in) No§
WAV Yes (built-in) Yes - SDL_sound 1.2 (internal)7,
AIFF No Yes - SDL_sound 1.2 (internal)7,

- SDL 1.2 is not actively maintained any more.
† - 22.05 kHz, 44.1 kHz, 48 kHz; mono, stereo
‡ - 44.1 kHz stereo only
§ - SDL_sound supports it, but the feature might be broken or DOSBox does not indicate support.

Development snapshot builds

Only Linux snapshots are available at the moment.

Pre-release builds can be downloaded from CI build artifacts. Go to Linux builds, select a build you are interested in, click "Artifacts" button (in the top right), and download the package.

Snapshots are dynamically-linked x86_64 builds, you'll need additional packages installed via your package manager. Different dependencies might be necessary for specific snapshots (check included README file).

Fedora

$ sudo dnf install SDL SDL_net opusfile

Debian, Ubuntu

$ sudo apt install libsdl1.2 sdl-net1.2 opusfile

Arch, Manjaro

$  sudo pacman -S sdl sdl_net opusfile

Build instructions

Linux, macOS, MSYS2, MinGW, other OSes

Read INSTALL file for a general summary about dependencies and configure options. Read build.md for the comprehensive compilation guide.

$ git clone https://github.com/dreamer/dosbox-staging.git
$ cd dosbox-staging
$ ./autogen.sh
$ ./configure
$ make

You can also use a helper script ./scripts/build.sh, that performs builds for many useful scenarios (LTO, FDO, sanitizer builds, many others).

Visual Studio (2019 or newer)

First, you need to setup vcpkg to install build dependencies. Once vcpkg is installed and bootstrapped, open PowerShell, and run:

PS> .\vcpkg integrate install
PS> .\vcpkg install libpng sdl1 sdl1-net opusfile

These two steps will ensure that MSVC finds and links all dependencies.

Start Visual Studio, open file: vs\dosbox.sln and build all projects (Ctrl+Shift+B).

Interop with SVN

This repository is (deliberately) NOT git-svn compatible, this is a pure Git repo.

Commits landing in SVN upstream are imported to this repo in a timely manner, to the branches matching svn/* pattern, e.g. svn/trunk. You can safely use those branches to rebase your changes, and prepare patches using Git format-patch for sending upstream (it is easier and faster, than preparing patches manually).

Git tags matching pattern svn/* are pointing to the commits referenced by SVN "tag" paths at the time of creation.

Additionally, we attach some optional metadata to the commits imported from SVN in the form of Git notes. To fetch them, run:

$ git fetch origin "refs/notes/*:refs/notes/*"