Building all the prerequisites from source is a good way to waste a day of your life. Some of them are availalbe in the stock package repositries, such as libsdl and libogg, but the majority are not. I recommend downloading the tarball of static libraries I've compiled.
Supposing that you've downloaded the file to /Downloads, install the contents with the following commands: cd / ; tar xvJf /Downloads/OXC-mingw32-cross-tools.tar.xz. This will place a bunch of files in /usr/local/cross-tools/i386-mingw32.
On SDL_mixer website download SDL_mixer 1.2 source and SDL_mixer 1.2 Win32 32bits binaries. Extract the source in , you should get it in a directory such as \SDL_mixer-1.2.12. Create a \SDL_mixer-1.2.12\bin directory and extract the binaries here.
On SDL_image website download SDL_image 1.2 source and SDL_image 1.2 Win32 32bits binaries. Extract the source in , you should get it in a directory such as \SDL_image-1.2.12. Create a \SDL_image-1.2.12\bin directory and extract the binaries here.
On SDL_gfx website download last SDL_gfx source and extract it in . You should get it in a directory such as \SDL_gfx-2.0.24. Go to Other builds subdirectory and extract Makefile from mingw32.zip in the \SDL_gfx-2.0.24 directory. Edit the Makefile to modify it to have:
From the yaml-cpp website download a yaml-cpp source higher than 0.5.0, such as 0.5.1.From the CMake website download the CMake Windows zip binaries distribution.From the boost website download the current release.Extract the three archives in ; you should get directories such as \yaml-cpp-0.5.1, \cmake-22.214.171.124-win32-x86 and \boost_1_54_0
AppDep utility can be downloaded here.If you don't want to use it, just add a #Dependencies line at the end of your makefile, remove the AppDep call, and clear all lines after #Dependencies before using make depends.
Ok, I've gotten rid of dub and dub packages code. Just LoadLibraryA. All eight dlls work except for FreeImage.dll. I've compiled with dmd and -m64 option and freshly download a x64 FreeImage. Any Window users out there that use LoadLibraryA or FreeImage.dll?
First of all, it is worth understanding why a sdl2_mixer.dll file is missing and why sdl2_mixer.dll errors occur. It is widespread for users to encounter situations where software does not work due to flaws in .dll files.
Now you only need the OHRRPGCE source code. You can download a zip file from Source, but if you intend to make changes to the code and submit your improvements it's highly recommended that you use git or svn to download the source. Using git:
Don't download (e.g.) "gcc-5.2.0-for-FB-win32-gengcc.zip for -gen gcc" from the FB Downloads page, as this includes only gcc.exe and a couple libraries. You need a more complete build of GCC which includes g++, the C++ compiler (see next section).
You need the Windows SDK. Recent versions of Visual Studio include the Windows SDK (Visual Studio 2008 and later, and Visual Studio 2010 Express and later?) Different versions of Visual Studio support different versions of the SDK, so don't just download the latest SDK (see Q: What compiler toolset does a given Windows SDK support?.
First, download Code::Blocks from here. It is recommended to download a package that includes the compiler and debugger from MinGW pre-installed. Otherwise, in case you want to install each manually, you can find the MinGW installer here and the debugger here.
You need to download CMake from here. You can use either the installer or the zip file. The architecture types on the download page doesn't matter for 64-bit machines, since the 64-bit CMake binaries can create projects for either 32 or 64-bit binaries.
You need to download SDL2, SDL2_net, and SDL2_mixer for either Visual Studio (VC) or Code::Blocks (MinGW). It doesn't matter where you put them since you will use CMake to locate them. Though if preferred, you can place each of them in a folder called "sdl2" so you won't have to be hunting around for the libraries. If going in that direction, the folders might look like this:\sdl2\SDL2-2.0.12\\sdl2\SDL2_net-2.0.1\\sdl2\SDL2_mixer-2.0.4\
Sam Oscar Lantinga is a computer programmer. He used to be the lead software engineer at Blizzard Entertainment, where he was known to the community as Slouken. He is best known as the creator of the Simple DirectMedia Layer, a very popular open source multimedia programming library, and also developed the compatibility database for Executor, a proprietary Mac OS emulator. On this page you can find DLL files developed by Sam Lantinga. Currently we have 10 files in our database available for free download which you can use to fix missing dll errors. Below is a list of dll modules for Sam Lantinga software like; Simple DirectMedia Layer or other related Windows programs which use the same dll files.
Also you need to download and fetch the various files. This is made slightly more complicated because there are 32-bit and 64-bit versions and you want to keep them both so you can switch between the two.
You can download the official releases of PySDL2 from -sdl/py-sdl2/releases. Download the mostrecent release, unpack it and make sure that you installed the relevantprerequisites before continuing with the installation.
To quickly resolve your problem, we recommend download and use UNIDRV.dll Fix Tool. If you have technical experience and you want to install a DLL file manually, please select your version of Windows and download UNIDRV.dll, after that copy it to the appropriate place using the instruction below, it will fix dll errors.
If it's just the going through the code correcting the little things that Visual C throws a fit over, that's not a problem. If your talking about the accidental damage, that was with the "supposedly" protected system files ? How they became un-write-protected is still beyond me. I got VS2010 reinstalled, built a couple of my known good projects to make sure, and started working on things again, when I made a rude discovery ? The uninstall engine for Visual Studio is crap (or at least the 2010 and prior versions were.) Started getting random catastrophic failures of the IDE, and finally traced it to an "improper" uninstall prior to the re-install. Had to download Microshaf...um... Microsoft's special un-install program to rip all things VS out, so I could do a proper (and hopefully soon to be working right again,) install ? 041b061a72