Music Driver X (MDXDRV) format player using Simple DirectMedia Layer (SDL) version 2.0.x
This is actually a BouKiCHi project (https://github.com/BouKiCHi), but since I cannot find its repostory anymore, I would like to share here.
Music Driver X (MDXDRV) is a music driver developed by milk, K.MAEKAWA, Yatsube and Missy.M for SHARP X68000 home computers, it utilizes MML (Music Macro Language) to create music files capable of FM synthesis and ADPCM data wave replaying.
Call mdxplay with no arguments for a quick list of examples about how play a .MDX module.
Folder ${HOME}/.mdxplay/ on Linux o.s. or %USERPROFILE%\.mdxplay\ on Windows o.s. can be used to have .PDX files in a common folder.
The following steps build build mdxplay.exe on a MSYS2/MinGW-w64 box, or mdxplay on a GNU/Linux box, using SDL2 library (sdl2-config) and make.
$ git clone https://github.com/gzaffin/mdxmini.git
$ cd mdxmini
$ make mdxplay
The following steps build mdxplay on a Ubuntu/Debian/GNU/Linux box, using SDL2 library (pck-config) and cmake.
$ git clone https://github.com/gzaffin/mdxmini.git
$ cd mdxmini
$ mkdir build
$ cd build
$ cmake -D CMAKE_BUILD_TYPE=Release ..
$ make mdxplay
The following steps build mdxplay.exe on a MSYS2/MinGW-w64 Windows o.s. box with SDL2 and cmake.
$ git clone https://github.com/gzaffin/mdxmini.git
$ cd mdxmini
$ mkdir build
$ cd build
$ cmake -G "MSYS Makefiles" -D CMAKE_BUILD_TYPE=Release ..
$ make mdxplay
If MSYS Makefiles generator set with -G "MSYS Makefiles" cannot properly set make-utility,
then add -D CMAKE_MAKE_PROGRAM=<[PATH]/make-utility> PATH of make-utility (see [1])
$ git clone https://github.com/gzaffin/mdxmini.git
$ cd mdxmini
$ mkdir build
$ cd build
$ cmake -G "MSYS Makefiles" -D CMAKE_MAKE_PROGRAM=mingw32-make ..
$ cmake --build . --config Release --target mdxplay
The following steps build mdxplay.exe on a Windows o.s. box with MSVC, vcpkg, SDL2 installed with vcpkg.
You can have Your build environment set, on a Windows 10 box, if Your MSVC is Microsoft Visual Studio 2019 Community edition, using Windows 10 taskbar search box writing x64 Native Tools Command Prompt for VS 2019 and starting matching App.
Otherwise, if MSVC is installed in default localtion, if Windows SDK is 10.0.18362.0 (please see what is in 'C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs\Microsoft.UniversalCRT.Debug' folder) (see [2]) issuing
C:\Users\gzaff>"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64 10.0.18362.0
Then
C:\>"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\cmd\git" clone https://github.com/gzaffin/mdxmini.git
C:\>cd mdxmini
C:\mdxmini>mkdir build
C:\mdxmini>cd build
C:\mdxmini\build>cmake -G Ninja -D CMAKE_BUILD_TYPE=Release -D CMAKE_TOOLCHAIN_FILE=C:/Users/gzaff/Devs/vcpkg/scripts/buildsystems/vcpkg.cmake ..
C:\mdxmini\build>ninja mdxplay
For the case that Visual Studio can be used
C:\>"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\cmd\git" clone https://github.com/gzaffin/mdxmini.git
C:\>cd mdxmini
C:\mdxmini>mkdir build
C:\mdxmini>cd build
C:\mdxmini\build>cmake -G "Visual Studio 16 2019" -A x64 -T host=x64 -D CMAKE_TOOLCHAIN_FILE=C:/Users/gzaff/Devs/vcpkg/scripts/buildsystems/vcpkg.cmake ..
For building from command line
C:\mdxmini\build>cmake --build . --config Release --target mdxplay
Otherwise start Microsoft Visual Studio and debug mdxmini solution.
You can have Your build environment set, on a Windows 7 box, if Your MSVC is Microsoft Visual Studio 2017 Community edition, using Windows 7 taskbar search box writing x64 Native Tools Command Prompt for VS 2017 and starting matching App.
Otherwise, if MSVC is installed in default localtion, if Windows SDK is 10.0.17763.0 (please see what is in 'C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs\Microsoft.UniversalCRT.Debug' folder) (see [2]) issuing
C:\Users\gzaff>"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64 10.0.17763.0
Then
C:\>"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\cmd\git" clone https://github.com/gzaffin/mdxmini.git
C:\>cd mdxmini
C:\mdxmini>mkdir build
C:\mdxmini>cd build
C:\mdxmini\build>cmake -G Ninja -D CMAKE_BUILD_TYPE=Release -D CMAKE_TOOLCHAIN_FILE=C:/Users/gzaff/Devs/vcpkg/scripts/buildsystems/vcpkg.cmake ..
C:\mdxmini\build>ninja mdxmini
For the case that Visual Studio can be used
C:\>"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\cmd\git" clone https://github.com/gzaffin/mdxmini.git
C:\>cd mdxmini
C:\mdxmini>mkdir build
C:\mdxmini>cd build
C:\mdxmini\build>cmake -G "Visual Studio 15 2017 Win64" -T host=x64 -D CMAKE_TOOLCHAIN_FILE=C:/Users/gzaff/Devs/vcpkg/scripts/buildsystems/vcpkg.cmake ..
For building from command line
C:\mdxmini\build>cmake --build . --config Release --target mdxplay
Otherwise start Microsoft Visual Studio and debug mdxmini solution.
Recap of required MACRO definitions:
CMAKE_TOOLCHAIN_FILE: full PATH of vcpkg.cmake
SDL2_DIR: PATH to find SDL2Config.cmake
[1]
it is make-utility name e.g. mingw32-make with specified PATH if make is not within search PATH as it should be
[2] calling vcvarsall.bat update PATH variable, so "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake" and "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja\ninja" can be called as cmake and ninja respectively
Reference information pages about how to install and how to use Vcpkg