Microsoft Visual C++ |
First of all, install Microsoft Visual C++ Express 2008. You will also need the latest DirectX SDK installed (get it from Microsoft). It is recommended to install it in \projects\DirectX SDK (see below for further folder information). Installing an SVN client is a good idea, too. TortoiseSVN, which integrates with the Windows Explorer, is a good choice. The default installation folders are
For the default installation, the projects and programs\d2x-xl folders have to be located in the root folder of the installation drive (e.g. c:\projects and c:\programs\d2x-xl). The involved projects only use relative paths, but if you want to change the general structure of the installation or have the program folder somewhere else, you need to manually change the compiler include paths and linker output directories for all projects contained in the D2X-XL solution. Download all required source archives (you may want to place them in the projects folder):
Extract the library source archives to \projects\libraries and the D2X-XL source code to \projects\d2x-xl\trunk. Make sure to extract the folders contained in the archives. When done, you should have the following folders (which in turn should have a varying number of subfolders):
You will also need a D2X-XL installation in \programs\D2, so create one there or copy an existing over there. Launch Visual Studio. If it's the first launch:
Otherwise
To build the program and required DLLs, right click on "d2x-xl" in the solution explorer pane and:
or
If the linker complains about missing libraries, you will have to manually make Visual Studio build them. right click on the project name (E.g. SDL_mixer) and select "build". If the solution has been successfully built, simply press F5 to launch the debugger and run the program in it. The debugger will stop the program and display the code line causing the problem if it encounters any run time errors. That is, unless the problem is caused by code outside of D2X-XL or any of the libraries contained in its solution. In that case, open the call stack window (chose "Debug" -> "Windows" -> "Call Stack" from the menu) to see where the problem occurred. |