dosemu2 installation instructions (from source) ============================================== -> REQUIREMENTS for dosemu2: - fdpp of the latest version, for now from git or from PPA: https://code.launchpad.net/~dosemu2/+archive/ubuntu/ppa of from COPR: https://copr.fedorainfracloud.org/coprs/stsp/dosemu2/ - gcc >= 3.3 or clang >= 3.7.0 - glibc >= 2.20 - linux >= 3.16 for x86-64, >= 4.7 recommended. With older version than 3.16 there may be some problems with DPMI, especially make sure to not use 3.14 and 3.15. linux >= 4.3 for i386. linux >= 4.11 if you want to run 32bit dosemu under x86_64 kernel with multilib environment (you likely don't want to do this). - x86 (i386/x86-64) target CPU - bison and flex - SDL >= 2.0.6, >= 2.0.15 is recommended (older versions may not have scaling filters and KMS rendering working). - udev >= 240 recommended for KVM (execution acceleration) - libslirp >= 4.1.0 recommended for networking - json-c >= 0.13 recommended - development libraries: Xext, slang, gpm, alsa, fluidsynth, ladspa, libao can be used when available. This means that Ubuntu Focal or Fedora 31 are the minimum recommended systems. -------------------------------------------------------------------------- 1. Compile -------------------------------------------------------------------------- First you should run: ./autogen.sh Then either: ./default-configure make or - create a seperate directory and run $SRCDIR/configure (or $SRCDIR/default-configure; see below) make in that directory. - sudo make install You can now start dosemu2 using "dosemu". -------------------------------------------------------------------------- 2. Want to use a different configuration ? -------------------------------------------------------------------------- Runtime configuration variables can be stored in the file ~/.dosemu/.dosemurc. This file overrides the dosemu.conf file which is usually either in /etc/dosemu or in /etc. By default, most error and debug messages are logged to the file ~/.dosemu/boot.log. If you want a dosemu2 executable with development settings (debug info, experimental features, and so on) then it is easier to use the file compiletime-settings.devel -- you can use it by running ./default-configure -d (*not* ./configure -d) prior to running make.